Remove 'Rolling Tag' logic for Prereleases#86
Merged
Conversation
aidanheerdegen
approved these changes
May 24, 2024
Member
aidanheerdegen
left a comment
There was a problem hiding this comment.
LGTM assuming we still tag again on merge.
Member
Author
|
Indeed we do. That is handled in build-cd/.github/workflows/cd.yml Lines 25 to 47 in 06ed17b |
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We are removing the rolling tag logic because it is causing
spack installs to fail. This is because when updating the repository inspack, it fails togit fetch --tagsbecause it would clobber the existing tags.Removes functionality introduced in the CI (back when it was a part of the model) in ACCESS-NRI/ACCESS-OM2#47
In this PR:
References #85