Commits in GitKraken

[Lars-]

First of all: wow it works great in the CLI, this is going to save me a lot of time.

Is it possible to make it work in GitKraken as well? I have set the hook, and it is recognized by the client, but I need to type a commit message before I can click the commit button.
GitKraken then says that the hook exited with error code 127. In the logs I see this: /usr/bin/env 'node': file or folder doesn't exist. When I execute /usr/bin/env node in my terminal it works, so GitKraken seems to have some sort of other context.

I tried changing the first line of the hook to #!/home/lars/.nvm/versions/node/v16.18.1/bin/node (since that is the full path to my node executable). GitKraken then says that the hook executed succesfully, but it didn't change the commit text that I needed to type to be able to click on the commit button...

What to do to fix this? Or what can I do to debug this further?

[Lars-]

I actually think that I may have found something already. In /src/commands/prepare-commit-msg-hook.ts on line 18, you check if the commit message is already set and stops the execution if it is. Since I need to type something to actually commit, this would always disable opencommit.

[Lars-]

Removing that from the hook and changing the first line to my full node path enabled it. It would be great if line 18 is optional (maybe configurable per project via the cli) and the first line should contain the full path to node to work with GitKraken (maybe globally configurable via the cli)

[Lars-]

I created #19 for the configurable line 18 check, but I don't know how to fix the node path error.
It seems that GitKraken doesn't know the environment variables at all, so /usr/bin/env doesn't work there.

[sukharev-deel]

wow, that's great research! now i see what #19 is about, nice. let me check it one more time

[sukharev-deel]

have you tried this https://stackoverflow.com/a/26320915? may solve the 'node': file or folder doesn't exist issue

[Lars-]

have you tried this https://stackoverflow.com/a/26320915? may solve the 'node': file or folder doesn't exist issue

I just tried it, but that doesn't work either, since you call /usr/bin/env node. The /usr/bin/env part is the problem. But a workaround that actually works great is to simply change the hook and since it's a symlink, it's automagically changed for all projects, so it works now, but it's a bit of a hacky way haha.

[di-sukharev]

@Lars- thats great, could you close the issue pls <3