Repository navigation
Rebuild dev binary automatically when local main moves - #26
Merged
Merged
Conversation
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.
The dev binary went stale whenever
mainmoved, andpost-mergecan't catch it:mainis often detached, and finished work lands withgit branch -f main. Areference-transactionhook fires on every ref update.refs/heads/mainupdate and always exits 0scripts/rebuildDevBinary.go: builds fromgit archive main, so the active worktree doesn't matter, then installs atomicallygo tool task main-hook:install. It symlinks the hook, soscripts/changes take effect without re-installinggo tool task main-hook:uninstallremoves it, and so doesgo tool task use-brew//usr/bin/env go runfirst line,//go:build ignore), outside the normal build🤖 Generated with Claude Code