dosubot[bot] commented on issue #8680: URL: https://github.com/apache/incubator-devlake/issues/8680#issuecomment-3732309441
<!-- Greeting --> Hi @klind! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the incubator-devlake team. <!-- Answer --> DevLake does not filter out private repositories if your token has the correct scopes; it simply displays what the GitHub API returns for your authenticated user. For classic tokens, make sure your token includes the `repo`, `read:user`, and `read:org` scopes. If you’re using a fine-grained token, it needs all relevant read permissions for the resources you want to access (like Actions, Contents, Issues, Metadata, Pull requests, etc.)—missing any of these can cause private repos to be hidden, even if the token works with curl for direct repo access [[source]](https://github.com/apache/incubator-devlake/issues/8389). If your token is correct, try comparing the raw GitHub API response (using curl) with what DevLake displays. If private repos show up in the API response but not in DevLake, the issue may be in how DevLake parses or displays the data. Enabling debug logging or checking backend logs during the "Add data scope" step can help spot any errors or warnings related to token usage or API calls [[source]](https://github.com/apache/incubator-devlake/issues/8505). If everything looks correct but private repos still don’t appear, it’s likely a backend parsing or frontend display issue rather than a token or GitHub API problem. In that case, capturing logs or discrepancies will help pinpoint the cause. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/1b8a2ca0-a227-4fa6-b14d-1f49ae698366?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1b8a2ca0-a227-4fa6-b14d-1f49ae698366?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1b8a2ca0-a227-4fa6-b14d-1f49ae698366?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1b8a2ca0-a227-4fa6-b14d-1f49ae698366?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1b8a2ca0-a227-4fa6-b14d-1f49ae698366?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1b8a2ca0-a227-4fa6-b14d-1f49ae698366?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1b8a2ca0-a227-4fa6-b14d-1f49ae698366?feedback_type=other)</sup> [](https://app.dosu.dev/b4e8e847-d479-4541-83a8-d88d83fea5c9/ask?utm_source=github) [](https://cursor.com/link/prompt?text=DevLake%20does%20not%20filter%20out%20private%20repositories%20if%20your%20token%20has%20the%20correct%20scopes%3B%20it%20simply%20displays%20what%20the%20GitHub%20API%20returns%20for%20your%20authenticated%20user.%20For%20classic%20tokens%2C%20make%20sure%20your%20token%20includes%20the%20%60repo%60%2C%20%60read%3Auser%60%2C%20and%20%60read%3Aorg%60%20scopes.%20If%20you%E2%80%99re%20using%20a%20fine-grained%20token%2C%20it%20needs%20all%20relevant%20read%20permissions%20for%20the%20resources%20you%20want%20to%20access%20%28like%20Actions%2C%20Contents%2C%20Issues%2C%20Metadata%2C%20Pull%20requests%2C%20etc.%29%E2%80%94missing%20any%20of%20these%20can%20cause%20private%20repos%20to%20be%20hidden%2C%20even%20if%20the%20token%20works%20with%20curl%20 for%20direct%20repo%20access%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/incubator-devlake/issues/8389%29.%0A%0AIf%20your%20token%20is%20correct%2C%20try%20comparing%20the%20raw%20GitHub%20API%20response%20%28using%20curl%29%20with%20what%20DevLake%20displays.%20If%20private%20repos%20show%20up%20in%20the%20API%20response%20but%20not%20in%20DevLake%2C%20the%20issue%20may%20be%20in%20how%20DevLake%20parses%20or%20displays%20the%20data.%20Enabling%20debug%20logging%20or%20checking%20backend%20logs%20during%20the%20%22Add%20data%20scope%22%20step%20can%20help%20spot%20any%20errors%20or%20warnings%20related%20to%20token%20usage%20or%20API%20calls%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/incubator-devlake/issues/8505%29.%0A%0AIf%20everything%20looks%20correct%20but%20private%20repos%20still%20don%E2%80%99t%20appear%2C%20it%E2%80%99s%20likely%20a%20backend%20parsing%20or%20frontend%20display%20issue%20rather%20than%20a%20token%20or%20GitHub%20API%20problem.%20In%20that%20 case%2C%20capturing%20logs%20or%20discrepancies%20will%20help%20pinpoint%20the%20cause.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/incubator-devlake/issues/8680) -- 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]
