This repository has no description
Something went wrong. Try again.
fix(ci): don't delete update-flake-lock branch on failed merge master
The merge job deleted the PR branch unconditionally after attempting the squash merge, even when the merge itself failed (e.g. HTTP 405). That's why PR #8 closed with the branch gone but no commit landed - the merge failed and cleanup ran anyway. Now the branch is only deleted after a confirmed 200/201, and the job exits non-zero on any other outcome so it's visible in the run status instead of silently continuing. Also add a concurrency group, since update/build/push/schedule/PR triggers overlapping could race two merge attempts against the same PR.
Author Collin Diekvoss Date (Aug 20, 2026, 8:14 PM UTC) Commit 9ecbe117 9ecbe117715b7e8d2d376511aba33dcc2fdb7bcd Parent 1a629c99 1a629c99d5d027ae8e990f4d5760d5c109e1c2c4 Change ID qklntunw qklntunwqqytmtsrmnzzzlqwvrxulvvz