Skip to content
Browse files

Only push the tag not the changes when bumping version

When the tag build fails, we have already pushed the changes to master. This is
bad because no releases will be created. Instead only push the tag to the
repo, and later when the build succeeds push to the master branch. We don't
care if the build is than failing on the master branch. Since the release have
already been created and is available. So the MELPA package can be safely
  • Loading branch information...
cslux committed Jun 24, 2019
1 parent 7169ed5 commit ede2b54bc05066ad9baf48219f6a9023cb76892f
Showing with 16 additions and 2 deletions.
  1. +16 −2 scripts/
@@ -6,6 +6,7 @@ DIR="$(dirname $SCRIPT)"
MAJOR=$(echo $1 | awk -F. '{print $1}')
MINOR=$(echo $1 | awk -F. '{print $2}')
PROTOCOL=$(echo $1 | awk -F. '{print $3}')


@@ -55,5 +56,18 @@ git commit -m "Bump version to ${MAJOR}.${MINOR}" \
CMakeLists.txt \
src/rtags.el \
git tag -a "v${MAJOR}.${MINOR}" -m "RTags release ${MAJOR}.${MINOR}"
git push --follow-tags
git tag -a $TAG -m "RTags release ${MAJOR}.${MINOR}"

# Only push the tag in case the travis build fails.
# Procedure:
# - while :
# git tag -a $TAG -m "RTags release ${MAJOR}.${MINOR}"
# git push refs/tags/$TAG
# if build succeeds
# git push (push refs to master)
# break
# else
# git tag --delete $TAG
# git push --prune refs/tags/$TAG
git push refs/tags/$TAG

0 comments on commit ede2b54

Please sign in to comment.
You can’t perform that action at this time.