Skip to content

docs: require needs-go-port for deferred Go ports #672

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
Wibias merged 2 commits into from
Jul 29, 2026
Merged

docs: require needs-go-port for deferred Go ports #672

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f743bf6
docs: require needs-go-port for deferred Go ports
Wibias Jul 29, 2026
23ff099
docs: mirror needs-go-port in AGENTS Transition summary
Wibias Jul 29, 2026
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: 2 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,8 +67,8 @@ A merge into `dev` does not finish the task. The merging maintainer also
rebases that work onto `dev2-go`, ports whatever needs a Go counterpart under
`go/`, and merges the port. The item is done only when both lines carry the
change. If a change has no Go counterpart, say so in the merge or tracking
issue; if the port has to wait, open a tracking issue against `dev2-go` naming
the source commits before closing out the `dev` merge.
issue; if the port has to wait, open a `needs-go-port` tracking issue against
`dev2-go` naming the source commits before closing out the `dev` merge.
[`MAINTAINERS.md`](./MAINTAINERS.md) holds the authoritative wording.

The Claude Desktop integration formerly carried on the `claudedesktop` branch is
Expand Down
4 changes: 3 additions & 1 deletion MAINTAINERS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,9 @@ rule is written out under [Review and merge policy](#review-and-merge-policy).
indistinguishable from a forgotten one.
- If the port cannot be completed immediately (a blocking dependency, a
subsystem the port has not reached), open a tracking issue against
`dev2-go` before closing out the `dev` merge, and name the source commits.
`dev2-go` before closing out the `dev` merge, label it `needs-go-port`,
and name the source commits. That label is the durable signal that a
Comment on lines +48 to +49

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add the new label to the transition summary

When a maintainer relies on the repository's AGENTS.md transition summary, the deferred-port workflow still says only to open an issue and name the source commits, so following that documented workflow produces an unlabeled issue and defeats the durable triage signal introduced here. Update that summary to require needs-go-port as well, as the commit description intended, so the two policy surfaces do not prescribe different completion criteria.

AGENTS.md reference: AGENTS.md:L66-L72

Useful? React with 👍 / 👎.

deferred port is intentional, not forgotten.
- A pull request requires approval from at least one maintainer and successful required CI checks
before merge.
- Authors do not approve their own pull requests.
Expand Down
Loading