Skip to content
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

Open
laurentsimon opened this issue Nov 23, 2022 · 6 comments
Open

doc: update doc on use of PAT for private repositories #1020

laurentsimon opened this issue Nov 23, 2022 · 6 comments

Comments

@laurentsimon
Copy link
Contributor

We need to verify whether PATs are still needed for private repositories, and update the doc if they are not.

@LeviPesin
Copy link

They are still needed.

@laurentsimon
Copy link
Contributor Author

Thank you! Closing.

@laurentsimon
Copy link
Contributor Author

laurentsimon commented Dec 6, 2022

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.

@joshjohanning
Copy link

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 permissions lines, which obviously yields 'findings' from this scan action.

@laurentsimon
Copy link
Contributor Author

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.

@joshjohanning
Copy link

I think the PAT is needed for the branch protection check.

ahh that makes sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants