You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/skills/PR_WORKFLOW.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,10 +3,6 @@
3
3
Please read this in full and do not skip sections.
4
4
This is the single source of truth for the maintainer PR workflow.
5
5
6
-
## Triage order
7
-
8
-
Process PRs **oldest to newest**. Older PRs are more likely to have merge conflicts and stale dependencies; resolving them first keeps the queue healthy and avoids snowballing rebase pain.
9
-
10
6
## Working rule
11
7
12
8
Skills execute workflow. Maintainers provide judgment.
@@ -110,7 +106,7 @@ Before any substantive review or prep work, **always rebase the PR branch onto c
110
106
- During `prepare-pr`, use concise, action-oriented subjects **without** PR numbers or thanks; reserve `(#<PR>) thanks @<pr-author>` for the final merge/squash commit.
111
107
- Group related changes; avoid bundling unrelated refactors.
112
108
- Changelog workflow: keep the latest released version at the top (no `Unreleased`); after publishing, bump the version and start a new top section.
113
-
- When working on a PR: add a changelog entry with the PR number and thank the contributor (mandatory in this workflow).
109
+
- When working on a PR: add a changelog entry line with the PR number `(#<PR>)`and `thanks @<pr-author>` when author metadata is available (mandatory in this workflow).
114
110
- When working on an issue: reference the issue in the changelog entry.
115
111
- In this workflow, changelog is always required even for internal/test-only changes.
-`CHANGELOG.md` must include a newly added changelog entry line.
80
+
- When PR author metadata is available, that same changelog entry line must include `(#<PR>) thanks @<pr-author>`.
81
+
77
82
4. Commit scoped changes
78
83
79
84
Use concise, action-oriented subject lines without PR numbers/thanks. The final merge/squash commit is the only place we include PR numbers and contributor thanks.
0 commit comments