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
{{ message }}
Repository navigation
refactor\(source-control\)!: remove resolve-conflicts in favour of the pull-request conflict mode - part 3 of 3 #13199
Part 3 of 3 of #13138, split at intake (owner Q93). The done-when below is copied from #13138 as written.
Done when
plugins/source-control/README.md, docs/skill-cheat-sheet.md:229, plugins/work-items/skills/ship/actions/run.md:81 and its eval, and docs/upstream/mattpocock-skills.md:55,58 (which still says "keep ours pending an eval") are updated to the removal.
rg -n 'source-control:resolve-conflicts' plugins docs .github --glob '!**/CHANGELOG.md' --glob '!.changes/**' finds nothing, and node --test '.github/scripts/pr-unblock/*.test.mjs' exits 0 in the PR's CI.
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: #13197, #13198
I understood this as part 3 of 3 of #13138, which removes source-control:resolve-conflicts. This part updates the remaining docs, the ship action and its eval, and the upstream note. It is done when the rg search finds no references and the pr-unblock tests pass in CI. The scope is clear. The part 1 and part 2 issues (#13197, #13198) are siblings, not duplicates. I listed them as blockers because the final grep check can only pass once the removal itself has landed.
Not admitted to the issue lane: merged pull request #13256 names it with Refs: after its newest decision or refinement comment, so its work may already be done: close the issue if it is, or post a comment whose first line is **Decision recorded.** saying what is left, which sends it back through intake. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).
The PR's own CI never selected the pr-unblock suites (#13256 touches no pr-unblock file), so item 2 is settled by this run at the merge commit; #13266 tracks that gap in pr-verify.
Activity
github-actions commentedon Nov 4, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: #13197, #13198
I understood this as part 3 of 3 of #13138, which removes source-control:resolve-conflicts. This part updates the remaining docs, the ship action and its eval, and the upstream note. It is done when the
rgsearch finds no references and the pr-unblock tests pass in CI. The scope is clear. The part 1 and part 2 issues (#13197, #13198) are siblings, not duplicates. I listed them as blockers because the final grep check can only pass once the removal itself has landed.Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 4, 2026
Not admitted to the issue lane: merged pull request #13256 names it with
Refs:after its newest decision or refinement comment, so its work may already be done: close the issue if it is, or post a comment whose first line is**Decision recorded.**saying what is left, which sends it back through intake. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).kyle-sexton commentedon Nov 4, 2026
Delivered: closing as completed.
Agent choice, not an owner answer.
docs/skill-cheat-sheet.md,plugins/work-items/skills/ship/actions/run.mdand its eval, anddocs/upstream/mattpocock-skills.mdupdated to the removal): delivered by refactor(source-control)!: remove resolve-conflicts in favour of the pull-request conflict mode #13256 (merge commit 9b3f10f); its pr-verify note records this item delivered in full.rg -n 'source-control:resolve-conflicts' plugins docs .github --glob '!**/CHANGELOG.md' --glob '!.changes/**': no matches (exit 1).node --test '.github/scripts/pr-unblock/*.test.mjs': tests 1326, pass 1326, fail 0.The PR's own CI never selected the pr-unblock suites (#13256 touches no pr-unblock file), so item 2 is settled by this run at the merge commit; #13266 tracks that gap in pr-verify.
kyle-sexton commentedon Nov 4, 2026
Closing on the delivery record above (issuecomment-6634167843): both items met at merge commit 9b3f10f.