Code Review Process

Expectation for a Good Pull Request

• PRs should be relatively small and focused on a single feature, refactoring part or a bug fix.
• Clear descriptions of changes, why they were made and what are the expected outcomes.
• (Optional, but recommended) Provide a screenshot or a video recording if the PR is about a UI feature.
• Must pass all tests and CI checks. The PR must have a line coverage of at least 80% to ensure edge cases are covered.
• Must be linked to an issue so that when it is merged, the issue is automatically closed (and can be reopened if needed).

Review guidelines

• Ensure code readability.
• Ensure no hard-coded values are present.
• Ensure that the documentation is present and is exhaustive.
• Ensure that SonarQube does not detect any code smells or that security hotspots are properly addressed.
• Ensure adherence to coding standards.