![]() ![]() For example, if your tag starts with a V, as in V3.2.2, then you might use RELTAG=$(git describe -tags -long -always -dirty='-*' -match 'V*.*' 2>/dev/null)` in the `.git/hooks/post. If your tag starts with anything other than a number, then you need to change the -match part accordingly. One reason your release tag might not be as you intend could be because it isn't being picked up by RELTAG=$(git describe -tags -long -always -dirty='-*' -match '*.*' 2>/dev/null)` in the `.git/hooks/post-.*įiles. Here is the file I have used for abc.tex \documentclass Git commit -m "updated release number in pdf" Git commit -m "my commit message goes here" ( start with clean repo, make changes to abc.tex and compile) git add abc.tex Here is a list of command line steps, that keeps the release number up to date (this assumes that abc.pdf has been committed at some point previously) The main assumption is that abc.pdf is being tracked by git. Only the following commit contains a correct set of data.Īs current workaround I am moving the tag after the PDF commit as described in this post. > When checking out "Release 1.34" the PDF has not the right info. The client shows commit changes in side by side text editors, where you can see the changes and rollback in a click. Is this supposed to be? Can somebody help me?Įdit: Added picture to specify my question.Īs shown in the screenshot (graphical log view of Smartgit) the commit where the tag is given and the commit where the pdf was added - containing the right release info - are not identical. I do not see different behaviour when using smartgit or commandline tool git. As consequence: when checking out the version where the tag is given, the PDF does not contain the tag. dlgSgPreferences.lbl'Local and Remote Changes'Local and Remote Changes: dlgSgPreferences. Provide here the full path to the installed 'git' executable. When I am following it, the given tag in the commit history is "one behind". In order to use all SmartGit functionality, you need to have command line Git installed on your system. My question: How can the Git tag be aligned with the formatted PDF? The described workflow is showing two commits. Format
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |