Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get Travis to check if the version number matches the tag number #296

Merged
merged 1 commit into from
Oct 25, 2016

Conversation

gemmaleigh
Copy link
Contributor

@gemmaleigh gemmaleigh commented Oct 20, 2016

If it does, don't update the latest-release branch.
Otherwise, if the version number has changed - update the latest release branch.

- If it does, don’t update the latest release branch.
@gemmaleigh
Copy link
Contributor Author

gemmaleigh commented Oct 20, 2016

If you'd like to test this, I commented out lines 10 & 11 and 28 to 30.

This can then be run locally:

./update-release-branch.sh

The output is:

++ cat VERSION.txt
+ VERSION_TAG=4.0.0
+ git rev-parse 4.0.0
+ echo 'Not updating the latest-release branch as the tag already exists...'
Not updating the latest-release branch as the tag already exists...

cc. @robinwhittleton @joelanman

Lines 10 & 11 check:

  • we want this to only happen from our repo, not forks
  • check this is not a pull request
  • check we're on the master branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants