Conversation
Collaborator
Author
|
n.b: I first did this many months ago... maybe it should be re-run again to get the latest recommended version of things. |
nevans
added
workflows
github_actions
nevans
force-pushed
the
configure-trusted-publisher
branch
from
9082a45 to
cbe3044
Compare
This was copied from what I've been using with `net-imap`. The action will automatically trigger when `v*` tags are pushed. And I've configured the `rubygems.org` environment to require a reviewer to confirm, before actually executing the action (self-review _is_ allowed). It attempts to creates a draft release after the deploy completes. GitHub wouldn't let me add the `resque` "Core" team as reviewers... but I've also configured the environment so that organization admins can bypass the protection rules, so I suppose that doesn't really matter! This way, in the extremely unlikely event that an emergency release is required and I can't be contacted (or I've moved on, without a proper handoff), any `resque` organization admin can make a new release by simply bumping the `VERSION` contant, pushing the tag, and reviewing the action.
nevans
force-pushed
the
configure-trusted-publisher
branch
from
cbe3044 to
cba979c
Compare
Collaborator
Author
Updated to be almost identical to how I've configured |
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
1 participant
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 was copied from what I've been using with
net-imap.The action will automatically trigger when
v*tags are pushed. And I've configured therubygems.orgenvironment to require a reviewer to confirm, before actually executing the action (self-review is allowed). It attempts to creates a draft release after the deploy completes.GitHub wouldn't let me add the
resque"Core" team as reviewers... but I've also configured the environment so that organization admins can bypass the protection rules, so I suppose that doesn't really matter!This way, in the extremely unlikely event that an emergency release is required and I can't be contacted (or I've moved on, without a proper handoff), any
resqueorganization admin can make a new release by simply bumping theVERSIONcontant, pushing the tag, and reviewing the action.