Skip to content

fix(ci): make fork patch retirement explicit - #171

Merged
incognitojam merged 2 commits into
mainfrom
t3code/explicit-fork-patch-retirement
Aug 16, 2026
Merged

fix(ci): make fork patch retirement explicit#171
incognitojam merged 2 commits into
mainfrom
t3code/explicit-fork-patch-retirement

Conversation

@incognitojam

Copy link
Copy Markdown
Collaborator

What changed

Fork Nightly now reapplies upstream-equivalent commits and stops when a fork patch becomes empty, making patch retirement a maintainer-reviewed decision. Successful rebases add a compact patch range-diff to the workflow summary.

When a rebased candidate has the same tree as the released nightly but newer ancestry or a reviewed patch retirement, the workflow now promotes that candidate to main without publishing another release. It no longer restores the older nightly history.

Focused Git fixtures cover clean replay, upstream patch adoption, content conflicts, range-diff reporting, and tree-equivalent promotion through the real backup and lease script.

Verification

  • vp test run scripts/rebase-onto-upstream.test.ts scripts/check-source-stack.test.ts
  • vp run --filter @t3tools/scripts typecheck
  • vp lint scripts/rebase-onto-upstream.test.ts --report-unused-disable-directives
  • shellcheck .github/scripts/rebase-onto-upstream.sh .github/scripts/check-source-stack.sh
  • git diff --check

Written by an agent (T3 Code, gpt-5.6-sol).

@incognitojam
incognitojam merged commit 34125bb into main Aug 16, 2026
9 checks passed
@incognitojam
incognitojam deleted the t3code/explicit-fork-patch-retirement branch August 16, 2026 12:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant