-
Notifications
You must be signed in to change notification settings - Fork 11
chore(deps): bump the pre-commit group with 9 updates #1190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
dependabot
wants to merge
1
commit into
main
Choose a base branch
from
dependabot/pre_commit/main/pre-commit-24844c79d7
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+8
−8
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Investigate why this change has the same version tag with different hashes. The same happens below for flake8 and actionlint.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We introduced the original sha
dda8db18cfc68df532abf33b185ecd12d5b7b326with PR #1156, and I’m almost certainly sure that at that time the sha was the valid commit sha for tag1.20.0. However, now that original commit sha adamchainz/blacken-docs@dda8db1 does not exist; instead, tag 1.20.0 points at commit adamchainz/blacken-docs@fda7769. 1 And so, Dependabot now updates therevto the latest and correct sha while keeping the tag the same.If I had to make a guess then I’d say that the repo’s history was force-pushed at some point and the tag
1.20.0was reassigned to a different commit, though I can’t see that in the activities here. @adamchainz might be able to shed some light on this?Remains the question why
pre-commitaccepts an invalid revdda8db1without a warning and then seems to clone the latest tag:I didn’t find this behavior documented here, and I didn’t find an issue discussing handling of an invalid/nonexistent
revhere. However, following thepre-commitcode inStore.clone()here I can reproduce the behavior with plaingit:If I use a random other commit sha:
So
git“knows” something here, and I’m still unclear howgitmanages to connect these two commit shas 🤔Footnotes
Note also that the repo has moved, as per comment here. ↩