Pre-commit hooks such as `lefthook` cause an error saying `env: node: No such file or directory`

[0-CAT]

Describe the bug

When using a pre-commit hook such as lefthook, it is impossible to commit due to a popup error indicating that node was not found.

To Reproduce

1. Create a new folder and open the terminal.
2. Run Terminal commands:

echo "node_modules\n.DS_Store" > .gitignore
git init
git add -A
git commit -m "Initialize repo"
npm install --save-dev lefthook

3. Replace the contents of lefthook.yml with the following content:

pre-commit:
  commands:
    check:
      glob: "*.{txt}"
      run: node -v

4. Run Terminal commands:

git add -A && git commit -m "Add lefthook"
echo Test > README.md

5. Open the above created repository in Gitnuro.
6. Stage README.md and add a commit message.
7. Click "Commit".

An error saying that node cannot be found will be shown, even if Node is installed and available on the terminal path. (It even works if I pop open a terminal from Gitnuro and run node -v or git commit.)

Expected behavior

The commit hook should run exactly as it does if using git commit from the CLI, and no error should be shown.

Screenshots

Desktop (please complete the following information):

OS: macOS 15.1
Gitnuro version: 1.3.1

[xoniq]

Has this been resolved yet? I try to use a pre-commit hook to set the timestamp in a file, which then is used in my project to reload assets to cache based on that, so cache refreshes with new builds.

But I cannot use git binary in the githook when it goes via Gitnuro. Tried git, /bin/git, /usr/bin/git nothing works.

It does work perfectly fine when I use git commit -m "xx" on my terminal. So its isolated to how Gitnuro handles this.

[JetpackDuba]

Hello! I haven't tried it yet, sorry. I'll try to give some feedback during the weekend.

[xoniq]

Hello! I haven't tried it yet, sorry. I'll try to give some feedback during the weekend.

I have tested it on macOS, with the same pre-commit hook, there it works. I had some other unrelated issues with my Mint installation, so decided to go new install with it.

ully new Linux Mint 22 installation, same pre-commit hook, clean flatpack Gitnuro install, exactly the same issue on exec git add.

[JetpackDuba]

That's probably due to Flatpak sandboxing, it's a different issue. As a workaround, does it work if you add this before the git command? /usr/bin/flatpak-spawn --host --env=TERM=xterm-256color

[xoniq]

I'll try that. I normally always install via DEB files, I'll try it soon, will be at home soon. I'll reply to this with the result, so future people might find this.

[xoniq]

@JetpackDuba thank you so much, that was it. For reference, this is what I use:

exec /usr/bin/flatpak-spawn --host --env=TERM=xterm-256color git add .....