Skip to content

fix(plan-lifecycle): accept merged PullRequest ClosedEvent closer in archive - #25

Merged
DocksDocks merged 2 commits into
mainfrom
fix/archive-pull-request-closer
Aug 24, 2026
Merged

fix(plan-lifecycle): accept merged PullRequest ClosedEvent closer in archive#25
DocksDocks merged 2 commits into
mainfrom
fix/archive-pull-request-closer

Conversation

@DocksDocks

Copy link
Copy Markdown
Owner

Refs #22

plan.mjs archive refused the legitimately merged closing PR on live GitHub: the excludeUserLinked connection came back empty for a same-repository keyword closer, and the ClosedEvent closer arrived as a PullRequest node, which the verifier ignored (Commit only). Observed live while archiving #22.

  • Read the PullRequest closer from the timeline and verify it with the existing merged-into-default-branch rule.
  • An unmerged or wrong-branch closer is still refused; the earlier-commit supersession rule is unchanged.
  • CLI tests: merged closer passes, wrong-branch closer refused, bare closer keeps failing with the accurate refusal.

Verification: plan-cli contract suite and scripts/ci.mjs --plugin plan-lifecycle exit 0; live plan.mjs archive 22 now prints plan #22 finished (closed by …/pull/24).

…archive

GitHub classifies some same-repository keyword closers as user-linked and
returns an empty excludeUserLinked connection, while the ClosedEvent closer
arrives as a PullRequest node rather than a Commit. archive ignored that
closer and refused a legitimately merged closing pull request (observed live
on #22). Read the PullRequest closer from the timeline and
verify it with the same merged-into-default-branch rule; an unmerged or
wrong-branch closer is still refused.
@DocksDocks
DocksDocks merged commit 145ed6c into main Aug 24, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant