ci: skip release-please job when secret is not defined#530
Open
ci: skip release-please job when secret is not defined#530
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
baywet
force-pushed
the
ci/release-please-condition
branch
from
ed3e4ae to
2728ef3
Compare
|
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.
The release-please workflow fails in forks or environments where
RELEASE_PLEASE_TOKEN_PROVIDER_PEMis not configured, erroring at the GitHub App token generation step.Changes
Added an
ifcondition to skip the release job when the secret is absent:Mirrors the fix from kiota-authentication-oauth-ruby#49.