On command line, git commit executes pre-commit hooks as expected.
That is, first pre-commit command is executed, after that, commit is done.
On sublime merge gui, when I commit using gui, it commits first, then, pre-commit is executed, which is not wanted and intended. For same reason, even just after commit, there are new changes in sublime merge gui, which are made by pre-commit.
Version info
=== App Version Information ===
Build: 2068
=== Git Version Information ===
Using Git: git (system)
git version 2.30.1 (Apple Git-130)
PATH: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin (from shell)
environment variables loaded using: /bin/zsh -l
=== Browse Page Information ===
HEAD: f04845b56b16279b0517ae9a6e117ba40ac7c8b6
Is in merge: 0
Is in cherry_pick: 0
Is in rebase: 0
Is in revert: 0
On command line, git commit executes pre-commit hooks as expected. That is, first pre-commit command is executed, after that, commit is done.
On sublime merge gui, when I commit using gui, it commits first, then, pre-commit is executed, which is not wanted and intended. For same reason, even just after commit, there are new changes in sublime merge gui, which are made by pre-commit.
Version info
=== App Version Information === Build: 2068
=== Git Version Information === Using Git: git (system) git version 2.30.1 (Apple Git-130) PATH: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin (from shell) environment variables loaded using: /bin/zsh -l
=== Browse Page Information === HEAD: f04845b56b16279b0517ae9a6e117ba40ac7c8b6 Is in merge: 0 Is in cherry_pick: 0 Is in rebase: 0 Is in revert: 0