Skip to content

mz-commit: require a Linear issue reference on every PR #37847

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
ohbadiah wants to merge 1 commit into from
Open

mz-commit: require a Linear issue reference on every PR #37847

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
9 changes: 6 additions & 3 deletions .agents/skills/mz-commit/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,9 +52,12 @@ Never regenerate the entire Cargo.lock — bare `cargo update` bumps every semve

GitHub is public. Linear is not.

* Link the Linear issue a PR addresses with a magic word and bare ID
in the PR description, e.g. `Closes CS-639`. A branch name
containing the issue ID links the PR even without a magic word.
* Every PR links a Linear issue with a magic word and bare ID in the
PR description, e.g. `Closes CS-639`. A branch name containing the
issue ID links the PR even without a magic word.
* Exception: a docs-only change needs no issue. Say so in the
description with a parenthetical: "(No Linear reference: docs-only
change.)"
* Closing words move the issue to Done when the PR merges:
close(s/d/ing), fix(es/ed/ing), resolve(s/d/ing), complete(s/d/ing),
implement(s/ed/ing).
Expand Down
Loading