Repository navigation
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
GitHub's pull_request synchronize event only fires when a PR's own head ref changes, so pushing a fix to the bottom of a stacked PR chain never retriggers CI for anything built on top of it. This repo currently has a real, live stacked chain sitting on stale CI for exactly this reason. This script cascades a fix through the chain automatically: give it the bottom branch, it walks the chain via gh pr list --base (so it stays correct as PRs are added or merged out, not a hardcoded list), merges each branch into the next, and pushes. It stops at the first real conflict rather than cascading past it, since everything above a broken link depends on content that link never actually delivered. Went with a plain script over the gh stack extension deliberately: this repo isn't ExaDev-only, and a third-party CLI extension only some contributors have installed isn't a good default for a shared workflow. This uses only git/gh, matching the plain gh pr create --base stacking convention already in use here.
Mearman
force-pushed
the
tooling/restack-stacked-prs
branch
from
October 25, 2026 09:23
1cdee58 to
21c4b70
Compare
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.
GitHub's pull_request
synchronizeevent only fires when a PR's own head ref changes, so pushing a fix to the bottom of a stacked PR chain never retriggers CI for anything built on top of it. This repo currently has a real, open stacked chain sitting on stale CI for exactly this reason.This script cascades a fix through the chain automatically: give it the bottom branch, it walks the chain via
gh pr list --base(so it stays correct as PRs are added or merged out, not a hardcoded list), merges each branch into the next, and pushes. It stops at the first real conflict rather than cascading past it, since everything above a broken link depends on content that link never actually delivered.Went with a plain script over the
gh stackextension deliberately: this repo isn't ExaDev-only, and a third-party CLI extension only some contributors have installed isn't a good default for a shared workflow. This uses onlygit/gh, matching the plaingh pr create --basestacking convention already in use here. Same script as cluster-api-v2#251, which hit the identical problem.