Skip to content

docs: CONTRIBUTING (integration branch policy) #3

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
casibbald merged 1 commit into from
Oct 27, 2026
Merged

docs: CONTRIBUTING (integration branch policy) #3

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
17 changes: 17 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Contributing to this fork

This repository is a fork. Its integration branch is `master`: it carries every
change made in this fork, and it is the only branch that projects depending on
the fork should consume (a dependent can follow just one branch).

- **Changes land here first.** Every fix or feature goes to `master` through a pull
request merged with a merge commit. Branches that dependents pin are never
rebased or force-pushed.
- **Upstream proposals are cut separately.** Once a change is on `master`, the
pull request for the upstream project is cut fresh from upstream's default
branch as a single-purpose change (one concern, one commit, following
upstream's conventions). It is not merged from `master`.
- **Upstream is merged in regularly.** Upstream's default branch is merged into
`master` so the fork stays a superset of upstream.
- **Before an upstream pull request merges or closes,** check that its content is
on `master` (by content, not commit hashes: upstream branches are re-cut).
Loading