build: Emit rerun-if-changed for branch file on ref: HEAD
#1224
Conversation
This file contains 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
We already ran into the issue of git hashes not updating when checked out to a branch, because the `HEAD` file doesn't change. `HEAD` does however tell us what branch (ref) the user is checked out to, which is a file much like `HEAD` containing the hash of the commit it is currently pointing to, and will inevitably change if the user "moves around" (ie. rebasing or committing). Emitting a `rerun-if-changed` on this file should make the git hash much more reliable.
sdroege
approved these changes
Sep 22, 2021
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.
We already ran into the issue of git hashes not updating when checked out to a branch, because the
HEADfile doesn't change.HEADdoes however tell us what branch (ref) the user is checked out to, which is a file much likeHEADcontaining the hash of the commit it is currently pointing to, and will inevitably change if the user "moves around" (ie. rebasing or committing). Emitting arerun-if-changedon this file should make the git hash much more reliable.