diff options
author | David Kaspar [Dee'Kej] <dkaspar@redhat.com> | 2018-08-06 13:25:13 +0200 |
---|---|---|
committer | Dee'Kej <deekej@linuxmail.org> | 2018-08-07 08:10:26 +0200 |
commit | d641eae353a9725eb845c636ff893b0ad8b036f1 (patch) | |
tree | 9b02cd33af53a029756054a078ab4acdb8c3e94d | |
parent | 8c9e2d170ad4d86feb593cfccd3d58f450d3c085 (diff) | |
download | initscripts-d641eae353a9725eb845c636ff893b0ad8b036f1.tar initscripts-d641eae353a9725eb845c636ff893b0ad8b036f1.tar.gz initscripts-d641eae353a9725eb845c636ff893b0ad8b036f1.tar.bz2 initscripts-d641eae353a9725eb845c636ff893b0ad8b036f1.tar.xz initscripts-d641eae353a9725eb845c636ff893b0ad8b036f1.zip |
make release-commit: do not create tag automatically
GitHub will create a new commit with different hash (merge) when
applying the pull-request, and so the tag ended up pointing to wrong
commit hash...
For now we have to tag the release commits manually.
-rw-r--r-- | Makefile | 1 |
1 files changed, 0 insertions, 1 deletions
@@ -113,7 +113,6 @@ release-commit: @rm -f .changelog.tmp @git add initscripts.spec @git commit --message="$(NEXT_VERSION)" - @git tag -a -f -m "Tag as $(NEXT_VERSION)" $(NEXT_VERSION) @echo -e "\n New release commit ($(NEXT_VERSION)) created:\n" @git show |