Add 'hm lock update' and 'hm lock adopt' for lock-file-only pin updates - #1
Merged
Merged
Conversation
Two workflows previously required a full 'hm sync', which force-checks out
the configured ref and rewrites the checkout as a side effect:
hm lock update pin each repo to the latest commit on its configured
branch (git ls-remote; checkouts untouched; --sync also
moves checkouts)
hm lock adopt pin each repo to its current local HEAD; refuses an
unpushed HEAD unless --force, since 'hm sync --locked'
could not reproduce it elsewhere
Both support -p/--project, -t/--tag, and --dry-run. Repositories pinned to
a commit/tag in config are skipped by 'lock update'.
Also disable gpg signing in test-repo setup helpers so the suite does not
hang on pinentry when the developer's global config sets commit.gpgSign.
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
1 participant
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.
Two workflows previously required a full 'hm sync', which force-checks out the configured ref and rewrites the checkout as a side effect:
hm lock update pin each repo to the latest commit on its configured
branch (git ls-remote; checkouts untouched; --sync also
moves checkouts)
hm lock adopt pin each repo to its current local HEAD; refuses an
unpushed HEAD unless --force, since 'hm sync --locked'
could not reproduce it elsewhere
Both support -p/--project, -t/--tag, and --dry-run. Repositories pinned to a commit/tag in config are skipped by 'lock update'.
Also disable gpg signing in test-repo setup helpers so the suite does not hang on pinentry when the developer's global config sets commit.gpgSign.