Repository navigation
Conversation
Inventory the seven open pull requests and thirteen open issues, record the simulated stack conflicts, and specify unique-tree replay after the delivery-foundation squash so later PRs do not reintroduce bootstrap CI or unsafe React peer ranges. Co-authored-by: sykosyber <sykosyber@users.noreply.github.com>
sykosyber
marked this pull request as ready for review
September 6, 2026 00:14
Contributor
|
Closing this documentation-only PR as an execution aid that does not need to enter the application base. The branch and its merge simulations remain available for reference. #10 is already closed, #14 is now merged, and this session is executing cleanup. The recorded order is also stale: #11 now includes corrected #15 session handling and a reproduced/fixed tracker-401 privacy gap (3980d96); do not replay the older 0a56f3f CSV tree over that fix. PR #12 has a Windows-and-delivery integration prepared on codex/pr12-windows-delivery-ready (b19fedb), with local unit/API/browser checks passing. Current status and required approvals belong on the affected PRs rather than another 723-line planning merge. |
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.
Problem and result
Relay has seven open pull requests and thirteen open issues stacked on the same
main, several of which already contain the delivery foundation. Squash-merging them in GitHub number order would reintroduce bootstrap CI, conflict inpackage.json/vite.config.ts/ README public-copy markers, and land an unsafe React 19.2.6 + RSC 19.2.8 Dependabot bump.This adds the reviewed merge strategy and the step-by-step train:
docs/superpowers/specs/2026-09-06-merge-all-open-prs-design.mddocs/superpowers/plans/2026-09-06-merge-all-open-prs.mdOrder: close #10 → squash #14 → rebase #18 → unique-tree replay #13 → unique-tree replay #11 (README + integrations/README recipes) → rebase #12 with the Windows Node guard → rebase #15 without rewriting the unit-test script.
No application source, schema, or workflows change in this PR.
Evidence
2372771/aa3f2f4(recorded in the spec).docs/superpowers/does not overlap Establish protected CI/CD and authenticated production releases #14'sdocs/*.mdfiles).Review
This PR is not part of the application merge train. After it is reviewed, execute the plan on the existing product PRs. Agents cannot squash-merge; last-push human approval is still required.