When using a client and/or IDE with git integration built in, it's difficult to see a failed ruff commands until after a commit is pushed up. This change adds the ability to see those errors in your client and/or editors if you have the pre-commit hooks installed.
Note: This is purely opt-in (just install-hooks) and a user can bypass with --no-verify after it's installed. n.b. this pre-commit hook does have the potential to "lose" a commit message but many clients save the most recent commit (.git/COMMIT_EDITMSG) but this is generally a bug with the git client/implementation itself.
When using a client and/or IDE with
git
integration built in, it's difficult to see a failedruff
commands until after a commit is pushed up. This change adds the ability to see those errors in your client and/or editors if you have the pre-commit hooks installed.Note: This is purely opt-in (
just install-hooks
) and a user can bypass with--no-verify
after it's installed. n.b. this pre-commit hook does have the potential to "lose" a commit message but many clients save the most recent commit (.git/COMMIT_EDITMSG
) but this is generally a bug with thegit
client/implementation itself.git-fork
Before
After
lazygit