-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: update doc on use of PAT for private repositories #1020
Comments
They are still needed. |
Thank you! Closing. |
Sorry. Here we want to verify whether "normal PATs" are needed for private repositories. Thanks for the link on fine-grained tokens. They are not supported for GraphQL either, yet. |
What is the PAT needed for? In a test private repo, I was able to get this to work without a PAT. But I did comment out all of the |
I think the PAT is needed for the branch protection check. You can keep the permissions line and it should work still work, but except for the branch protection check. |
ahh that makes sense |
We need to verify whether PATs are still needed for private repositories, and update the doc if they are not.
The text was updated successfully, but these errors were encountered: