feat(build): request new ORG-level secrets #5
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.
What this PR changes/adds
This PR adds two new org-level secrets, the
GITHUB_BOT_TOKEN
and theGITHUB_BOT_USER
. Those secrets already exist on our Jenkins instance (namedBOTTOKEN
andBOT
), so we would simply like to migrate them to GitHub.Why it does that
We would like to be able to invoke workflows across repos, so e.g. our
Release
repo invokes a test workflow in theConnector
repo. For that we need a PAT on the ORG level.Further notes
GITHUB_BOT_TOKEN
(containing the bot's PAT) should be sufficient. I have no preference either way..gitignore
fileLinked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.