docs: record the enforced branch protection settings - #140
Merged
Merged
Conversation
`develop` had no branch protection at all, so the "no direct push" rule was policy only. It now mirrors `main`: pull request required, `tests-result` as the required status check, and force pushes and branch deletion blocked. `strict` is left off on `develop` so merging one PR does not invalidate every other open PR. Document both branches side by side, and note that `enforce_admins` is off on both — that is what keeps the post-release back-merge and semantic-release's `chore(release)` push working. Also correct the CI requirement: the required status check is `tests-result`, which aggregates the `tests` matrix; `lint-check` and `test-coverage` are pnpm scripts run inside that job, not check contexts.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Owner
Author
|
🎉 This PR is included in version 4.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
develophad no branch protection at all, so the "no direct push" rule inCLAUDE.mdwas policy only. It now mirrorsmain: pull request required,tests-resultas the required status check, and force pushes and branch deletion blocked.strictis left off ondevelopso merging one PR does not invalidate every other open PR.This documents both branches side by side and notes that
enforce_adminsis off on both — that is what keeps the post-release back-merge and semantic-release'schore(release)push working.It also corrects the CI requirement: the required status check is
tests-result, which aggregates thetestsmatrix.lint-checkandtest-coverageare pnpm scripts run inside that job, not check contexts.Docs only — semantic-release will not cut a version for this.