Skip to content

docs: encode the review & merge protocol (4 org rules) #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lyubomir-bozhinov merged 1 commit into from
Jul 22, 2026
Merged

docs: encode the review & merge protocol (4 org rules) #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,17 @@ commitward is defined by its [`CONTRACT.md`](CONTRACT.md): the interface, the in
guarantees other components rely on. A change that alters observable behavior updates the
contract **in the same PR**. Swappability is the point — don't break the socket.

## Review & merge protocol

Every repository in the [Barnett Studios](https://github.com/Barnett-Studios) family lands changes
under the same four rules — maintainers included:

1. **Change via PR.** All changes land through a pull request against `main`; no direct pushes.
2. **Green CI.** A PR merges only when every required CI check passes.
3. **A review.** A PR merges only with at least one approving review.
4. **Reviewer ≠ author.** The approving review must come from someone other than the PR's author —
no self-approval, no self-merge.

## Pull requests

1. Branch off `main` (fetch first — `main` moves).
Expand Down
Loading