feat: add workflow for publishing libraries after merge #4
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
Signed-off-by: Jason C. Nucciarone <[email protected]>
Signed-off-by: Jason C. Nucciarone <[email protected]>
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.
Title gives it away, but this pull request sets up the
release-libsworkflow forhpc-libs. Pretty much the same thing as the the workflow fromstorage-libs.I added a token to the repository secrets that will allow us to upload the
slurm_opslibrary. It will expire while we are in The Hague for the Engineering Sprint in October. I'm very tempted to write us a tool liketokenatorthat enables us to bulk refresh our repo secrets so it's not this weird song and dance when we try to publish new updates to Charmhub 😅Misc.
I added a .editorconfig file. Helps with consistency across IDE's. We can extend rules farther as we need to 😃