public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Wesley Schwengle <wesleys@opperschaap•net>
To: Git maillinglist <git@vger•kernel.org>
Subject: git hook question
Date: Fri, 29 May 2026 01:01:34 -0400	[thread overview]
Message-ID: <cc9fda14-d8e8-4982-9a3d-9aa816c0b90c@opperschaap.net> (raw)


Hello,

I added the following to my gitconfig:

hook.npm-test.event=pre-push
hook.npm-test.command=npm run test

This works well when I run `git hook run pre-push' but when using `git 
push' this breaks a little because it adds the remote and the location, 
as seen via `GIT_TRACE=1 git push origin':

00:46:53.714453 run-command.c:673       trace: run_command: 'npm run 
test' origin git@gitlab•com:waterkip/mything.git
00:46:53.714458 run-command.c:765       trace: start_command: /bin/sh -c 
'npm run test "$@"' 'npm run test' origin 
git@gitlab•com:waterkip/mything.git

I understand the why, normally pre-push gets `<local-ref> SP 
<local-object-name> SP <remote-ref> SP <remote-object-name> LF'. This 
has a similar feel, albeit a different syntax. The difference feels like 
a minor bug, but not one I'm worried about at this moment: you would 
expect it to get the same arguments/parameters as the regular pre-push 
hook. But I digress.

My actual question is: Is there a way to tell the hook "Don't give me 
arguments, just run the plain command that is defined". I looked in `man 
1 git-hook', but I was unable to find something that looks like it.


Cheers,
Wesley

-- 
Wesley Schwengle

next             reply	other threads:[~2026-05-29  5:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29  5:01 Wesley Schwengle [this message]
2026-05-29  5:21 ` git hook question Jeff King
2026-05-29 16:11   ` Wesley Schwengle
2026-05-29 16:22     ` Wesley
2026-05-29 17:52     ` Ben Knoble
2026-05-29 19:23     ` Jeff King
     [not found]       ` <4d938e1e-fdd3-42d6-a879-4d394ee8c00d@opperschaap.net>
2026-05-29 21:00         ` Jeff King
2026-06-03 13:07           ` Adrian Ratiu
2026-06-01  5:33   ` Junio C Hamano
2026-06-01  5:55     ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc9fda14-d8e8-4982-9a3d-9aa816c0b90c@opperschaap.net \
    --to=wesleys@opperschaap$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox