You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3f8c957
Browse filesBrowse the repository at this point in the historyBrowse files
* Follow server base changes in sync and rebase
* Handle retargets across stack commands
* Document automatic base retargeting
* Validate retarget cutoffs and recovery
* Normalize retarget comparisons in view
* Avoid false retarget consent prompts
* Keep view's retarget check best-effort
* Require consent before dropping unlanded merged branches
A merged branch below a retargeted stack can land in the old base after that
base merged. Check the boundary the cascade drops, and skip the prompt only
when those commits reached the new base.
* Keep the old base when importing a retargeted stack
Importing onto GitHub's new base hid the pending retarget, so the next rebase
skipped consent. Keep the merged first PR's base so sync repairs the stack, and
compare GitHub's base only for the tracked-stack warning.
0 commit comments