async-post-commit-hook-commit-orphaned-by-squash-merge

A branch showing `[ahead 1]` after a squash merge usually means a local commit never reached the remote. With an async post-commit hook, the hook's commit lands after your push completes, so it exists only locally and was never part of the PR.

Inspect the orphaned commit with `git show <sha>` to confirm it has valuable content, then create a fresh branch off origin/main and run `git cherry-pick <sha>`. Fold the cherry-picked commit into your next PR so the content lands on main.

An async post-commit hook runs in the background after each commit and creates its own follow-up commit, such as auto-generated docs or a site regen. Because it runs asynchronously, `git push` does not wait for it, so the hook's commit often misses the push.

No. Inspect the ahead commits first with `git log --oneline` and `git show` before deleting. If a commit carries real content like a corrected design doc, cherry-pick it onto a fresh branch off origin/main before removing the merged branch.

Discard the orphan when it is noise, such as a no-op regeneration or content that is already correct on main. Rescue it only when it carries real, load-bearing content like a design doc corrected to match your merged change.