I ended up using icrond to launch my "hook" whenever a file
in /salt/.git/logs was modified, wich fill my need.
Thank you again!
On Monday, August 18, 2014 6:18:11 AM UTC-4, Konstantin Khomoutov wrote:
> On Fri, 15 Aug 2014 07:55:36 -0700 (PDT)
> > > > I'm trying to get my post-merge hook to run but I can't get it to
> > > > work.
> > > [...]
> > > > #git pull
> > > The merge did not happen because `git merge` (which was run as a
> > > part of the `git pull` work flow) performed a fast-forward.
> > That make sense.
> > Any other way to run a hook everytime I do a "git pull" ?
> I think no, there's no way to do that (you can try to find the word
> "pull" in the githooks manual page). But the next question is why you
> need to have a hook for this in the first place? Hooks can't be
> committed (and hence be made automatically available and armed in
> remote repositories) and hence they have to be considered to be "local
> configuration". If so, why not just have a wrapper program (a shell
> script could be the simplest way to make one) which calls `git pull`
> and dances around its outcome?
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.