Repository navigation
One PR per issue: update the open one instead of opening a second - #590
Merged
Merged
Conversation
Birfy
commented
Oct 21, 2026
Birfy
left a comment
Collaborator
Author
There was a problem hiding this comment.
Verdict: PASS at c053cca
Tip SHA: c053cca3bdd97ceea96f57ab37a94291fdd5f094
This records the owner's new hard rule (an issue that already has a PR keeps it; update that branch instead of opening a second) next to the admission line, so the two are read together. Scope decision: the owner's own request.
Diff (4 files, +7 -1, no code): `AGENTS.md` (new paragraph in the admission-line section, with the exception and the obligation to write the reason on the issue), `docs/code-standards.md` (bullet under "Merge only a reviewed tip"), `docs/autonomous-dev.md` (one sentence in the merge-by-tier item), `.claude/skills/fix-issue/SKILL.md` (bullet in step 4).
It applies to new work: #586 and the three originals it replaced are untouched, as the Chief asked.
Ran at the tip: CI all green (tests-ok, plugins social/tree/timeline, package, Node 24). On this tree: `node --test .github/scripts/*.test.mjs` 93/93, `check-arch-docs.mjs` with `ARCH_DOCS_BASE=HEAD~1` OK (4 files), `scripts/ds-bot-patches.mjs check` OK, `changelog.mjs check` OK. No fragment: a change users cannot see ships none. TZ=UTC.
Not run: one-shot `npm run verify` (2 GiB OOM), full core suite, smoke, Desktop.
Tier: **T3** (`AGENTS.md`, the policy docs). Enqueueing it myself under the rule it records. Any new commit voids the PASS.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Risk: T3 (
AGENTS.mdand the policy docs).The owner's new hard rule: when an issue already has a pull request, work in that one — do not open a second and close the first. This records it next to the admission line, so the two are read together.
What changes (4 files, +7 -1)
AGENTS.md: a new paragraph in the admission-line section — re-base the open branch, useupdate-branch, or push a commit to its head, and put the tests there too; a contributor's fork is treated the same while it allows maintainer edits; the only exception is a branch that cannot be pushed, and then the reason goes on the issue, never a silent swap.docs/code-standards.md: the same rule as a bullet under "Merge only a reviewed tip".docs/autonomous-dev.md: one sentence in the merge-by-tier item..claude/skills/fix-issue/SKILL.md: a bullet in step 4 (PR).It applies to new work from now on: #586 and its closed originals (#535/#539/#568) are left exactly as they are, as the Chief asked.
Checks
node --test .github/scripts/*.test.mjs— 93/93.check-arch-docs.mjswithARCH_DOCS_BASE=HEAD~1— OK (4 changed files).scripts/ds-bot-patches.mjs check— OK (no code touched).changelog.mjs check— OK; no fragment, a change users cannot see and that ships no code.TZ=UTC.Not run: one-shot
npm run verify(2 GiB OOM in this container), full core suite, smoke, Desktop.