docs: suggest using fine-grained PATs #1937
Open
+1
−1
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
|
Hi @jackkoenig I'm happy add information about using fine-grained PATs to this section of the documentation, but it should be a separate bullet point and not replace the existing advice. The reason for this is that fine-grained PATs are still in beta and not all GitHub APIs and processes support them yet. Some features of this action appear not to work with fine-grained PATs currently, such as this issue. So if I add it to the documentation it needs to come with a caveat that it may not work in all cases. |
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.
Fine-grained PATs fix a lot of the security issues with PATs so are worth suggesting (IMO): https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/.