-
Notifications
You must be signed in to change notification settings - Fork 4
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
Tag versions, add pre-commit example #16
Comments
Thank you for your feedback! I appreciate your effort! I have added I will try to address remaining issues when I find a moment. |
I just tried but ran into another issue. When I run But if I run the pre-commit hook I get a
I run Windows 11 + python 3.12 Do you have an idea what's the problem? |
Hi, nice project, I really like it!
A few things that should be added:
Tag versions as you release them
.pre-commit-config.yaml
expects arev
which is eitherAdd an pre-commit-config.yaml example
As mentioned above, the rev should ideally be the tag of the released version. At the time of opening this issue that would be 2.4.0
Add a
--version
or-V
argumentAfter installing its hard to figure out which version is installed.
Finally some questions 😄
I run
deadcode.exe .
locally and get: Well done! ✨ 🚀 ✨pip freeze | grep deadcode deadcode==2.4.0
If I add deadcode to my
pre-commit-config.yaml
like thisand run it manually with
pre-commit
, I get this:The sha sum
2706a6c1a4f3fd2d0c40daf066c681858cacd181
is the one with the commit message "Bump version to 2.4.0".So I guess that should be the code released, right!?
Why do they behave differently?
The text was updated successfully, but these errors were encountered: