So the file needs to be part of the repository because the application is 
installed by downloading the zipball directly from github... There is no 
"build process" per say.  Every push to the master branch is an offical 
release, and every push to the develop branch is a bleeding edge release.  I 
should say that this is web software that installs as a plugin into a CMS.

That being said, the problem with pre-commit is that the version won't be 
incremented until after the commit... but i guess that is really just a 
chicken and egg problem that i can't get rid of.

What i was hoping to do was just "amend" the previous commit without causing 
that second "amended" commit firing the post-commit hook.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to