On 2016-11-28 11:44, René J.V. Bertin wrote: > I presume that means they merge the development branch into master > before creating the release.
Maybe. I do not want to dive deep into the release workflow of other projects. > Possibly: > > %> port provides /opt/local/bin/git-release > /opt/local/bin/git-release is provided by: git-extras > > It does change something. Don't ask me the details but the 1 or 2 > times that I've tried to make a release which behaves correctly > w.r.t. git-describe I succeeded with that command, not by creating > the tag manually. IIRC it had something to do with getting the tag > pushed to the remote, which doesn't (necessarily) happen > automatically when you create a tag and then push. As far as I can see from a quick glance at the shell script, git-release is only a wrapper for this sequence of commands: .git/hooks/pre-release git commit ... git tag $1 ... git push $2 git push --tags $2 .git/hooks/post-release I don't see how that would change anything for 'git describe', if this is only done on a branch. Rainer
