docs(v2): deployment, add required Github token scope infos #3565
Conversation
This file contains 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
I did a fair amount of testing to ensure that this was the correct scope required. Unfortunately, I couldn't find a smaller subset of scopes that would give sufficient permission to deploy to GitHub Pages.
|
Deploy preview for docusaurus-2 ready! Built without sensitive environment variables with commit ca84f09 |
|
thanks, LGTM |
slorber
added
the
pr: documentation
slorber
changed the title
repo scope for PAT.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #3189
Motivation
Fix #3189 - clarify the necessary 'scope' required on the personal access token for deploying to GitHub pages through both Travis CI and Azure Pipelines
Have you read the Contributing Guidelines on pull requests?
Yes!
Test Plan
Because this is a documentation-only change, I haven't done any testing on the software itself. However, I performed manual testing to ensure the documentation change listed here is correct. The testing included:
Related PRs
N/A