Skip to content

Conversation

eugenk
Copy link
Member

@eugenk eugenk commented Jul 2, 2017

This shall fix #3 and builds on top of #9.

It fetches the latest tag from the repository, puts it as the default tag and then asks which tag to deploy. Simply pressing enter on this question will deploy the latest tag.

This tag-handling is only activated for the live stages (which will be ontohub.org), not for development stages (which are staging.ontohub.org and in the future, develop.ontohub.org).

Currently, it is set to deploy to staging.ontohub.org because I don't want to mess with ontohub.org until the re-implementation is ready.

@eugenk eugenk force-pushed the 3-check_if_deployment_branch_can_be_the_newest_tag branch from 87aa7d4 to 0ea90ed Compare July 10, 2017 12:19
@eugenk eugenk force-pushed the 3-check_if_deployment_branch_can_be_the_newest_tag branch from 0ea90ed to 2aee8f6 Compare July 14, 2017 11:40
@eugenk eugenk requested review from phyrog and ebolloff July 20, 2017 10:05
@eugenk eugenk mentioned this pull request Jul 20, 2017
@eugenk eugenk merged commit c7b552e into master Jul 20, 2017
@eugenk eugenk deleted the 3-check_if_deployment_branch_can_be_the_newest_tag branch July 20, 2017 14:45
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.

Check if deployment branch can be the newest tag
2 participants