I would recommend studying git.git's Makefile and seeing how they generate
their version file. It doesn't use a hook; it's part of the build.
--
David
On Apr 28, 2011, at 1:36 PM, Greg Moser wrote:
> So in my .git/hooks folder I have a file named post-c
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
On Thu, Apr 28, 2011 at 01:36:27PM -0700, Greg Moser wrote:
> So in my .git/hooks folder I have a file named post-commit that looks like
> this:
>
>
> #!/bin/sh
>
> rm version.txt -i
> git describe --tags >> version.txt
>
>
> Basically the idea being that after every commit, I write the "git
So in my .git/hooks folder I have a file named post-commit that looks like
this:
#!/bin/sh
rm version.txt -i
git describe --tags >> version.txt
Basically the idea being that after every commit, I write the "git describe"
to a file in my repository called version.txt. This script works fine
