dosubot[bot] commented on issue #8190:
URL: 
https://github.com/apache/incubator-devlake/issues/8190#issuecomment-2475875242

   <!-- Greeting -->
   Hey there, @GiesN! I'm here to help you with any bugs, questions, or 
contributions you have for the Apache DevLake project. Let's tackle this GitHub 
PAT issue together.
   
   <!-- Answer -->
   To resolve the issue with the GitHub PAT not working with your private 
GitHub organization in Apache DevLake, ensure that the PAT has the following 
permissions:
   
   - `repo`
   - `read:user`
   - `read:org`
   
   These permissions are necessary for accessing private repositories. 
Additionally, if you are using fine-grained personal access tokens, make sure 
the token is granted read-only permission for entities such as `Actions`, 
`Contents`, `Discussions`, `Issues`, `Metadata`, and `Pull requests`. Also, 
fine-grained PATs do not support GraphQL APIs, so you must disable `Use GraphQL 
APIs` on the connection page if you choose to use them, which may significantly 
increase data collection time 
<sup>[[1]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.16/Configuration/GitHub.md)</sup><sup>[[2]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.17/Configuration/GitHub.md)</sup>.
   
   If the permissions are correctly set and the issue persists, check if there 
are any specific error messages or logs that could provide more details on the 
problem. Starting from version 0.18.0, DevLake provides an auto-check for the 
permissions of your token(s), which might help identify any missing permissions 
<sup>[[3]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.21/Configuration/GitHub.md)</sup>.
   
   
   <!-- Dosu Comment Footer -->
   *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to