Not really following your point.  What I described could be implemented by a post-update hook that just ran &quot;git rev-parse HEAD&quot; and stuffed the result into a database somewhere.  If anything it&#x27;s significantly easier to implement than an authorization model.