You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Either I'm doing something silly or MOB_GIT_HOOKS_ENABLED is not respected.
I'm issuing mob start on some new branch. As expected, mob issues git commit --allow-empty -m 'mob start [ci-skip] [ci skip] [skip ci]'. But the --no-verify is missing, causing some hook to run (which is not desired) and fail (which is blocking).
A workaround would be to disable the hooks... which I don't like. Or to find an older version of mob that doesn't suffer this problem. But I'm not sure yet what version introduced this.
Hey @mightyiam thank you for that well described bug report. I think this bug was introduced with version 4.2.0. May you could check if it works with version 4.1.2. I think I also identified the line I need to change. But unfortunately I am on a weekend trip right now and do not have my computer with me. I will have a deeper look on Monday when I am back.
Either I'm doing something silly or MOB_GIT_HOOKS_ENABLED is not respected.
I'm issuing
mob start
on some new branch. As expected,mob
issuesgit commit --allow-empty -m 'mob start [ci-skip] [ci skip] [skip ci]'
. But the--no-verify
is missing, causing some hook to run (which is not desired) and fail (which is blocking).This, I figured by looking at the error line:
And I figured that MOB_GIT_HOOKS_ENABLED is false by default by running
mob config
:A workaround would be to disable the hooks... which I don't like. Or to find an older version of
mob
that doesn't suffer this problem. But I'm not sure yet what version introduced this.By the way, #374 may be the same issue.
The text was updated successfully, but these errors were encountered: