From: Stefan Monnier <monnier@iro•umontreal.ca>
To: git@vger•kernel.org
Subject: Re: Post-receive hook for "git pull"
Date: Fri, 12 Feb 2016 08:39:09 -0500 [thread overview]
Message-ID: <jwvlh6qt5i6.fsf-monnier+gmane.comp.version-control.git@gnu.org> (raw)
In-Reply-To: xmqqio4am3uk.fsf@gitster.mtv.corp.google.com
>> I have a system here where it can be quite common to have thousands of
>> branches in the remote repository, and where I'd like to update some
>> local state according to the appearance of new branches (or updates of
>> pre-existing ones).
>> Currently, I use a "git for-each-ref" after pulling and then check (for
>> each one of those refs) if an update is warranted, but this can get slow
>> with that many branches. Is there some way to get something like the
>> post-receive hook to be run for "git pull", so that the script gets told
>> directly which (remote tracking) branches have been modified/created?
> I do not think there is. But you could easily script along the
> lines of...
> #!/bin/sh
> git for-each-ref | sort >prestate
> git pull "$@"
> git for-each-ref | sort >poststate
> comm -12 prestate poststate
Right, it kinda works, but it can break down in case of
concurrent operations.
I really wish there was a way to get something like the post-receive
hook to be called everytime new commits are added, regardless if it's
due to a push, a pull, a commit, a fast-import, ...
Stefan
prev parent reply other threads:[~2016-02-12 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 13:47 Post-receive hook for "git pull" Stefan Monnier
2015-12-07 19:54 ` Junio C Hamano
2016-02-12 13:39 ` Stefan Monnier [this message]
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=jwvlh6qt5i6.fsf-monnier+gmane.comp.version-control.git@gnu.org \
--to=monnier@iro$(echo .)umontreal.ca \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox