Open
Conversation
Member
|
@nodejs/build-infra I'm asking similar questions in a few PRs related to adding tokens for access to sensitive build assets for GitHub workflows. It may just be that we should trust GitHub and we've already added equivalent tokens but I'd like to get input from other build team members on that front. |
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
2 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.
Main changes
credentials.jsonfor a environmental variableMAILGUN_API_KEYci.ymlto check that the changes are valid using--dry-runcd.ymlto apply the changes to MailgunNote
I will include the
MAILGUN_API_KEYsecret in the repository if we agree on it, as the pipelines will require itChangelog