Skip to content

Repository navigation

fix(docs): say a change to a managed file must be a fix or feat to ship #15

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

fix(docs): say a change to a managed file must be a fix or feat to ship #15

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
4 changes: 4 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,10 @@ markers, are kept in step with `studiobimo/project-template`. Change them there,
`make -C .devtools sync` brings the change in. `make -C .devtools drift` shows what differs, and a
weekly workflow opens an issue when something does. A deliberate difference goes in
`.template-ignore`, with a comment saying why.

Projects only receive a change at a release, and release-please releases only `fix`, `feat` and
breaking commits. A change to a managed file titled `chore`, `docs` or `ci` merges but never reaches
`sync`, so title it `fix` or `feat`.
<!-- <<< template:workflow -->

## Releases
Expand Down
Loading