atlantis testdrive => forking repo error : 401 Requires authentication

[Rico29]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Hello
When trying Atlantis testdrive, I get this error

# ./atlantis testdrive
Welcome to Atlantis testdrive!

This mode sets up Atlantis on a test repo so you can try it out. We will
- fork an example terraform project to your username
- install terraform (if not already in your PATH)
- install ngrok so we can expose Atlantis to GitHub
- start Atlantis

Press Ctrl-c at any time to exit


github.com username: <username>

To continue, we need you to create a GitHub personal access token
with "repo" scope so we can fork an example terraform project.

Follow these instructions to create a token (we don't store any tokens):
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#creating-a-fine-grained-personal-access-token
- use "atlantis" for the token description
- add "repo" scope
- copy the access token

GitHub access token (will be hidden): 
=> forking repo 
⠙Error: forking repo runatlantis/atlantis-example: POST https://api-github-com-gh.computerqwq.top/repos/runatlantis/atlantis-example/forks: 401 Requires authentication []

Regards

[dosubot]

Hi @Rico29! I'm Dosu and I’m helping the atlantis team.

The 401 error means your GitHub personal access token is missing, invalid, or doesn’t have the right permissions. For Atlantis testdrive, you need a token with the classic "repo" scope, or a fine-grained token with equivalent permissions for repository access and commit statuses. The documentation link can be confusing because it points to fine-grained tokens, but the "repo" scope is only for classic tokens. Make sure you:

• Create a classic token with the "repo" scope, or a fine-grained token that allows repository forking and commit status updates.
• Double-check for copy-paste errors or extra spaces when entering the token.
• Ensure your token hasn’t expired and your account doesn’t have SSO or 2FA restrictions that block token use.

If you use a fine-grained token, confirm it has access to public repositories and all necessary permissions for forking and status updates. If you still get the error after checking these, let me know what type of token you used and its permissions so I can help further.

References:

• Token requirements and common pitfalls
• Classic vs fine-grained token confusion
• 401 error root cause and troubleshooting

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}