Hi @sirwart , thanks for the great tool. I'm just writing up a book section on how to set up ripsecrets, via pre-commit, and I thought I'd try improve the instructions in the repo whilst I'm at it.
I made these improvements:
Improve some terminology - pre-commit uses "hooks" not "plugins"
Remove advice about updating regularly - I think this applies to all pre-commit users, who should be aware of the pre-commit autoupdate command, or use pre-commit.ci that runs this for you.
Show the sample config first, then explain the options.
Edit to recommend the ripsecrets hook, because since version 2.21.0, pre-commit can bootstrap Rust if it is unavailable (pre-commit PR, open docs improvement PR). This should make the ripsecrets hook preferable to ripsecrets-system.
Hi @sirwart , thanks for the great tool. I'm just writing up a book section on how to set up ripsecrets, via pre-commit, and I thought I'd try improve the instructions in the repo whilst I'm at it.
I made these improvements:
pre-commit autoupdate
command, or use pre-commit.ci that runs this for you.ripsecrets
hook, because since version 2.21.0, pre-commit can bootstrap Rust if it is unavailable (pre-commit PR, open docs improvement PR). This should make theripsecrets
hook preferable toripsecrets-system
.