Security and Collaboration

Repository Security Settings

To maintain the security and integrity of the codebase, the following settings are enforced for the repository:

1. Branch Protection Rule 1:

   • The main branch is protected.
   • No direct commits to main are allowed.
   • At least two approvals are required before merging a PR into main.

2. Branch Protection Rule 2:

   • The develop branch is protected.
   • No direct commits to develop are allowed.
   • At least two approvals are required before merging a PR into main.

3. Code Review and Approvals:

   • Every Pull Request must go through a code review process.
   • Two members of the team need to approve each PR before it can be merged.

4. Automated Testing:

   • Every procces of the CI/CD pipe must be completed before the merge can be done

Collaboration Guidelines

• Follow the branch naming conventions for clarity.
• Keep commits atomic and small, focusing on one change at a time.