-
Notifications
You must be signed in to change notification settings - Fork 107
/
create-release.sh
executable file
·38 lines (28 loc) · 1.41 KB
/
create-release.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
#!/bin/bash
set -e
REPO_PATH="alphagov/govuk_frontend_toolkit"
echo "Add config for alphagov/$REPO_PATH"
git config --global user.name "GOV.UK Design System CI"
git config --global user.email "[email protected]"
git remote add origin_ssh [email protected]:$REPO_PATH.git
# This openssl command was generated automatically by `travis encrypt-file`, see `.travis/README.md` for more details
openssl aes-256-cbc -K $encrypted_53be47f46000_key -iv $encrypted_53be47f46000_iv -in .travis/govuk_frontend_toolkit_push.enc -out ~/.ssh/id_rsa -d
chmod 600 ~/.ssh/id_rsa
echo "Check to see if the version file has been updated"
# get the version from the version file
VERSION_TAG="v`cat VERSION.txt`"
# Create a new tag - if the version file has been updated and a tag for that
# version doesn't already exist
# check to make sure the tag doesn't already exist
if ! git rev-parse $VERSION_TAG >/dev/null 2>&1; then
echo "Creating new tag: $VERSION_TAG"
# Create a new tag and push to Github
git tag $VERSION_TAG
git push origin_ssh $VERSION_TAG
# Alias branch for the most recently released tag, for easier diffing
# Force push local `master` branch to the `latest-release` branch on Github
git push --force origin_ssh master:latest-release
echo "Pushed latest-release branch to GitHub"
else
echo "Not creating a new tag, or updating the latest-release branch as the tag already exists..."
fi