pre-commit: `pre-commit autoupdate` should not change `rev` fields like `master` or `stable`
I set most of my hooks’ rev fields to master, or stable for black, see instructions. If I run pre-commit autoupdate, all rev fields are set explicitly to the latest version number, and I need to revert all them back manually. pre-commit autoupdate should update only those rev fields that are set to an explicit version number.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (9 by maintainers)
Commits related to this issue
- 🔧 Use the tag version for black in pre-commit The recent revisions of the pre-commit integration with black has specified to use the version instead of a constant branch name like `stable` so that i... — committed to chinnichaitanya/python-discord-logger by chinnichaitanya 3 years ago
- 🔧 Use the tag version for black in pre-commit The recent revisions of the pre-commit integration with black has specified to use the version instead of a constant branch name like `stable` so that i... — committed to chinnichaitanya/python-slack-logger by chinnichaitanya 3 years ago
OK, you convinced me, thanks.
I agree that reproducibility and repeatability is a very important concept when considering dependencies and build tools configuration, but (at least in my case) I’m using
pre-commitfor linting code, in case a linter is updated maybe I would get some new or different lint message, or even an error when committing, but my code would not really break. Or am I mistaken?