Re: pre-receive/update hook: how to know forced push?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


After some investigation of sources it seems to me 
decision to push changes to server or not is made by git client,
so server can only reject pushed updates.

Some examples of necessary detections can be found in
'contrib/hooks/post-receive-email' hook.

Sorry for the noise

> Hi, guys!
> 
> How to know in pre-receive hook that commit has been pushed with
> --force option?
> 
> I've written some pre-receive hook that denies pushed commits which
> have author's date earlier then current branch HEAD. It's done to
> prevent not triggering automated builds which are based on authors'
> timestamps.
> 
> But some time later I had to rollback branch to previous state.
> It is not convenient way to "git update-ref ..." on the server, I'd
> like to git push --force, but there is a question in the first
> sentence:
> 
> How to know in pre-receive hook that commit has been pushed with
> --force option?
> 
> Thanx in advance
> 

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Newbies FAQ]     [Linux Kernel Development]     [Free Online Dating]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Free Online Dating]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]     [Linux Resources]

Add to Google