Skip to content

Document PR title convention for CI-only PRs #20

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

Open
jnasbyupgrade wants to merge 1 commit into
base: master
Choose a base branch
from
+11 −0
Open

Document PR title convention for CI-only PRs #20

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 CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,14 @@ failures before treating the work as done:

Do not consider a push complete until its CI run is green (or the failure is
understood and explicitly accepted by the user).

## PR title convention for CI-only PRs

A PR whose diff is confined entirely to files under `.github/workflows/` gets a
title starting with `CI: ` (capital, colon, space). A PR that's CI-*motivated*
but also touches a real file elsewhere (a `bin/` script a workflow calls, a
linter's `Makefile` wiring, a submodule, etc.) is NOT CI-only under this
reading, even though CI is the reason it exists — don't stretch the prefix to
cover those. Check the actual file list
(`gh pr view <n> --json files --jq '.files[].path'`) before applying it, don't
guess from the title/description alone.
Loading