We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 55baf29 commit ee5139cCopy full SHA for ee5139c
docs/agile-development/branching-and-cicd.md
@@ -9,6 +9,7 @@ Purpose: Provide a concise, practical policy and examples teams can adopt for in
9
- Keep releases simple: use tags/releases from the integration branch and keep release process documented separately.
10
11
## Example branch protection rules
12
+
13
- Require at least one approving reviewer for pull requests.
14
- Require successful CI pipeline status checks before merge.
15
- Require up-to-date branch before merge if your policy prefers.
0 commit comments