3 check if deployment branch can be the newest tag #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.