top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Need to find out when a tag is pushed to a git server

+1 vote
322 views

We have a git server, all our team members can push to it, with the following command being executed in repository on git server, we can find out when a commit is pushed, except for tag, so my question is, any other way to find out when a tag is pushed to a git server?

git config core.logAllRefUpdates true

posted Aug 8, 2014 by Deepak Dasgupta

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+5 votes
Is there a way to know when the commit has been in the git server

I know form the "git log" we can now the commit time, but how to know when it is in the remote git server.

0 votes
Is there any reason why 'git clone -b' only takes a branch or a tag

Is there any reason why 'git clone -b' only takes a branch (from refs/heads/) or a tag (from refs/tags/) ?

Background: At $dayjob we're using some kind of 'hidden' refs (in refs/releases/) to communicate between the 'branch integrator' (who creates the ref in refs/releases/) and the 'build master' who wants to build that ref.

It would be a little easier if the build master could simply say

git clone -b refs/releases/the-release-for-today URL
instead of: git clone... ; cd ... ; git fetch... ; git checkout....

Any answer or even a better idea to solve that is appreciated.

0 votes
deletion of branch seems to modify tag as well in git...

$ git push origin :ABRANCHNAME
remote: Firing Pre - receive hook
remote:
remote:
remote: Firing Post receive hook
remote:
remote: Branch is ABRANCHNAME -- not creating Trigger file since this is not _int branch
remote: error: Trying to write ref refs/tags/ABRANCHNAME!SN-BL-20130605_100513_04363 with nonexistent object 0000000000000000000000000000000000000000
remote: fatal: refs/tags/ABRANCHNAME!SN-BL-20130605_100513_04363: cannot update the ref
To ssh://git@ourgitserver/repositoryname.git
- [deleted] ABRANCHNAME

I would not expect this behavior. Is git attempting to modify the tags associated to the HEAD commit on the branch in addition to the branch? If so, I would like to consider this a bug report...

...