From d641eae353a9725eb845c636ff893b0ad8b036f1 Mon Sep 17 00:00:00 2001
From: "David Kaspar [Dee'Kej]" <dkaspar@redhat.com>
Date: Mon, 6 Aug 2018 13:25:13 +0200
Subject: 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.
---
 Makefile | 1 -
 1 file changed, 1 deletion(-)

(limited to 'Makefile')

diff --git a/Makefile b/Makefile
index 20cf54ad..1114e579 100644
--- a/Makefile
+++ b/Makefile
@@ -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
 
-- 
cgit v1.2.1