[CI] Trigger CI on external PR #420#421
Closed
AliSoftware wants to merge 3 commits into
Closed
Conversation
…_client The use of the github_token under the hood was causing visibility problems about the token being mandatory and necessary to execute some actions on the API
At the moment of the release creation, the githubtoken can be passed as a parameter. In the cases that the param is nil or empty, we fallback to using the github_token from the runtime environment.
At the calling of the action the client has the possibility to use the githubtoken inside the create_relese action, the use is also documented in the ConfigItens
AliSoftware
added
the
Do Not Merge
AliSoftware
force-pushed
the
trigger-ci-external-pr/420
branch
from
a411015 to
4a8d792
Compare
Generated by 🚫 Danger |
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
3 participants
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 PR is only there to allow us to trigger the CI on #420 — since CI does not run on PRs involving forks (for security reasons).
This PR is thus not intended to be merged, and #420 will remain the PR on which all review and discussions will happen.