klind opened a new issue, #8680: URL: https://github.com/apache/incubator-devlake/issues/8680
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened - Downloaded docker-composer.yml sha256:7a96d8310d592a6cac2d8fe93f74f3cfa6e4905fe3c6e9e9b19bfd438f774875 env.example sha256:76032a42f7edaeae1d686d428c727a0eb9a914eb6776eae320846ff0ce47ebca - mv env.example .env - Set a secret in .env - docker-compose up -d I create a personal access token (classic) with access to private repos. Test the token against a private repo `curl -H "Authorization: Bearer ghp_tjowXLCSvZ2k34h234h234asdfasdf2" https://api.github.com/repos/<user>/<private repo>` In "Add data scope" step when setting up a connection I only see public repos. ### What do you expect to happen I expect to be able to choose a private repo when using a token that allows access to private repos ### How to reproduce See the steps under "What happened" ### Anything else _No response_ ### Version sha256:7a96d8310d592a6cac2d8fe93f74f3cfa6e4905fe3c6e9e9b19bfd438f774875 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
