Add release management workflows #85
Merged
Conversation
This file contains 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
nwiltsie
requested review from
tyamaguchi-ucla,
yashpatel6 and
Faizal-Eeman
as code owners
yashpatel6
approved these changes
Oct 8, 2024
Comment on lines
+19
to
+20
| # Secrets are only required until tool-create-release is made public | ||
| secrets: inherit |
There was a problem hiding this comment.
question (non-blocking): Can these be removed now that tool-create-release is public?
There was a problem hiding this comment.
We'll have to see - since I originally added that comment I started using our secret token to create the releases, so I'll have to play with it. I'll figure it out in the next few days and either remove the use of secrets or the comment saying that it's temporary.
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.
Description
This adds in the release management workflows from the newly-public /~https://github.com/uclahs-cds/tool-create-release.
Once we merge this PR I'm going to cut a new patch release to test everything; this is the first public repo to use those workflows so there may be a few rough edges to iron out.
Testing
No pipeline changes, no testing performed.
Checklist
I have read the code review guidelines and the code review best practice on GitHub check-list.
I have reviewed the Nextflow pipeline standards.
The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
I have set up or verified the branch protection rule following the github standards before opening this pull request.
I have added my name to the contributors listings in the
manifestblock in thenextflow.configas part of this pull request, am listedalready, or do not wish to be listed. (This acknowledgement is optional.)
I have added the changes included in this pull request to the
CHANGELOG.mdunder the next release version or unreleased, and updated the date.I have updated the version number in the
metadata.yamlandmanifestblock of thenextflow.configfile following semver, or the version number has already been updated. (Leave it unchecked if you are unsure about new version number and discuss it with the infrastructure team in this PR.)I have tested the pipeline using NFTest, or I have justified why I did not need to run NFTest above.