Skip to content

Upstream push loops forever when a retried item's own codeybox/<id> branch still holds a stale PR head - #704

Merged
AdamFrisby merged 2 commits into
mainfrom
codeybox/bd61e600
Oct 5, 2026
Merged

AdamFrisby merged 2 commits into
mainfrom
codeybox/bd61e600

Conversation

@AdamFrisby

Copy link
Copy Markdown
Owner

Automated via CodeyBox — work item bd61e6009d3449378d37afc6bd2920bc

Initiated by CodeyBox operator


Co-Authored-By: CodeyBox noreply@codeybox.invalid
🤖 Generated with CodeyBox

AdamFrisby and others added 2 commits October 5, 2026 12:17
…failing forever

Retried items recompose their work on a fresh base, so the remote
codeybox/<id> ref (the previous attempt's head) is never an ancestor of
the new head. The push step now treats owned branches distinctly from
merge conflicts: plain push on fast-forward, --force-with-lease against
the recorded last-pushed SHA on divergence, and a terminal park (new
upstream_blocked failure kind, non-retryable, never conflict-rework)
when the lease mismatches or no lease base exists. The lease helpers
refuse non-codeybox prefixes and work==base by exact match, and the
GitHub remote re-checks mergeability after the rewrite, supersedes
stale closed PRs with linked fresh ones, and resumes already-merged PRs
by forge proof. A startup scan plus GET/POST operator endpoints re-drive
stranded Failed/Merged items under the same rules. Legacy git hosts
degrade to the historical plain push.

    CodeyBox-Prompt-Revision: 1
    Co-Authored-By: CodeyBox <noreply@codeybox.invalid>
CodeyBox-WorkItem: bd61e6009d3449378d37afc6bd2920bc
CodeyBox-Agent: copilot/muse-spark-1.3-contributor
CodeyBox-Prompt-Revision: 1
Co-Authored-By: CodeyBox <noreply@codeybox.invalid>
@AdamFrisby
AdamFrisby merged commit d823a93 into main Oct 5, 2026
@AdamFrisby
AdamFrisby deleted the codeybox/bd61e600 branch October 5, 2026 13:50
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