It is recommended to use pipx run pre-commit instead of pipx install pre-commit. This ensures that the tool is run in an ephemeral environment with its latest version (or a specific version) without needing to permanently install it in the user's environment. This is cleaner and more in line with temporary usage patterns for pre-commit.
Currently, GEMINI.md mentions:
This can be done by running pre-commit install in your local repository.
It might be better to suggest pipx run pre-commit install or similar for users who don't want to install pre-commit globally.
It is recommended to use `pipx run pre-commit` instead of `pipx install pre-commit`. This ensures that the tool is run in an ephemeral environment with its latest version (or a specific version) without needing to permanently install it in the user's environment. This is cleaner and more in line with temporary usage patterns for pre-commit.
Currently, `GEMINI.md` mentions:
> This can be done by running `pre-commit install` in your local repository.
It might be better to suggest `pipx run pre-commit install` or similar for users who don't want to install `pre-commit` globally.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It is recommended to use
pipx run pre-commitinstead ofpipx install pre-commit. This ensures that the tool is run in an ephemeral environment with its latest version (or a specific version) without needing to permanently install it in the user's environment. This is cleaner and more in line with temporary usage patterns for pre-commit.Currently,
GEMINI.mdmentions:It might be better to suggest
pipx run pre-commit installor similar for users who don't want to installpre-commitglobally.