-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Error while migrating with multiple github token #34141
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
Comments
Git authorization was not taking into account multiple token feature, leading to auth failures Closes: #34141 --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
the entire GitHub migration was failing after this fix |
@VinothKumar-Ganesan |
@VinothKumar-Ganesan I also did a quick test, by using my personal access token |
Hi @wxiaoguang , i am using the gitea/gitea:nightly image and after filling the page and select migrate repository it was navigating to the following page |
What's your "access token" (I mean: what kind it is and how it is created)? It looks much shorter than mine ..... |
Hi @wxiaoguang , it was working fine now thanks for the support |
Glad to help. And special thanks to @TheFox0x7 for helping to investigate and fix the multiple token bug. Thank you all, I think this issue could be closed. |
Git authorization was not taking into account multiple token feature, leading to auth failures Closes: go-gitea/gitea#34141 --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> (cherry picked from commit 8a6df00c532becd4d10efb70827ccf80b2bf74e2)
Description
Gitea Version
1.23.6
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
docker
Database
None
The text was updated successfully, but these errors were encountered: