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
Give up cleanly when the recorded target branch is gone
The missing-target backstop returned silently, leaving the PR labeled with
no explanation and no path to ever resume. It now posts a comment and drops
the label like the other two dead-end cases, routed through a shared
abandon_resume helper.
# Continue processing after user manually resolved conflicts
211
221
continue_after_resolution() {
212
222
check_env_var "PR_BRANCH"
@@ -229,9 +239,7 @@ continue_after_resolution() {
229
239
MARKER=$(read_state_marker "$PR_BRANCH")
230
240
if [[ -z"$MARKER" ]];then
231
241
echo"⚠️ No autorestack state marker on $PR_BRANCH; cannot resume safely. Removing the label."
232
-
{ echo"ℹ️ autorestack could not find its state marker on this PR, so it will not update the stack automatically. If this PR still needs its base updated, do it manually."; } \
abandon_resume "$PR_BRANCH""ℹ️ autorestack could not find its state marker on this PR, so it will not update the stack automatically. If this PR still needs its base updated, update its base manually."
echo"⚠️ Recorded target branch '$NEW_TARGET' no longer exists; leaving $PR_BRANCH untouched."
269
+
echo"⚠️ Recorded target branch '$NEW_TARGET' no longer exists; abandoning resume of $PR_BRANCH."
270
+
abandon_resume "$PR_BRANCH""ℹ️ The branch this PR was being retargeted onto (\`$NEW_TARGET\`) no longer exists, so autorestack stepped back. If this PR still needs its base updated, update its base manually."
0 commit comments