![]() |
Git Tags - Printable Version +- webERP Forum (http://www.weberp.org/forum) +-- Forum: webERP Discussion (http://www.weberp.org/forum/forumdisplay.php?fid=1) +--- Forum: Development Discussion & Specification (http://www.weberp.org/forum/forumdisplay.php?fid=10) +--- Thread: Git Tags (/showthread.php?tid=8151) |
Git Tags - afcouling - 04-11-2018 I am working on a new changelog, in markdown format. I have been experimenting with git log, for quickly generating change notes in tabular markdown format, which can then be manually appended to the changelog. The beginnings of the new changelog can be found here. When running git log, I limit the 'timeframe' to particular commits, but it is necessary to know the commit references before doing this. It would be more convenient if I could run the git log query between/since a release tag. I have successfully pushed a tag to the 4.14.1 release commit on my fork. It it appears to be fine. Does anyone have any experience with using git tags? Are there any downside to their use, or any watch-outs? Andy. RE: Git Tags - TimSchofield - 04-11-2018 I created a tag on my repository to mark the point at which we agreed subversion ended. In my limited experience they are fine to use for exactly the purpose you propose. Have you read the official git book? It is free to download and very good RE: Git Tags - afcouling - 04-11-2018 Thanks Tim. I've read a few of the chapters on the git-scm website, but I should download a complete copy. Andy. RE: Git Tags - TimSchofield - 04-11-2018 Github actually sometimes calls tags releases in their interface so I would definitely say you were on the right tracks. One gotcha that I remember us that tags don't get pushed when you push to a remote such as Github you have to explicitly push them. I think from memory the command is git push origin tags But don't rely on my memory ![]() RE: Git Tags - afcouling - 04-11-2018 Quote:Github actually sometimes calls tags releases in their interface Yes, I noticed this. It's a little confusing. Pushing a tag seems to create a release, so I'd be reluctant to push a tag which didn't refer to a release commit. Some discussion on this subject here. RE: Git Tags - afcouling - 04-13-2018 I have identified commits associated with many of the previous releases. There were some releases for which I couldn't find any trace of a commit. Please see attachment. I propose to push tags to each of these. Andy. [attachment=817] |