...
Code Coverage
New code must have a coverage of 80% or greater unless explicitly noted otherwise in the story's acceptance criteria.
Static Code Analysis
All reported code smells, security vulnerabilities, and lint errors identified by SonarCloud and other CI pipeline tools must be fixed before merging code to the master branch.
There should be no code smells or security issues should be reported by SonarCloud upon merging.
Code uniformity
All new code should follow Code Uniformity standards
...
2. Pull Requests (PRs)
PR Descriptions
Every PR should include a detailed description with:
Purpose: The intent and objectives of the changes.
Approach: The methodology and reasoning behind the implementation.
Open Issues: Any unresolved questions or potential problems.
Approval Requirements
A minimum of two developers must approve each PR.
At least one approver must be a team lead or architect.
...