fix: update repo gob hash if git config mailmap content changes #26
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.
Summary
👋 This PR updates the gob hash in cache for a repository if the Git configuration
mailmap
setting is changed.Fixes an issue where updates to these configurations were not detected and caused the cache to become stale.
Reviewers
These changes can be tested with either local or global configurations and this branch to confirm the author matches the most recent changes to the mailmap:
These changes were tested with the following
git
version:Notes
The
log
format used before these changes respects.mailmap
and seems to also find Git configurations, even if--no-mailmap
is set:git-who/internal/git/cmd.go
Lines 17 to 18 in ae3a23c
Also interesting to note is that multiple formats for mailmap can be used at the same time! 📚 ✨