Gitea: Can't migrate from github without login + login does not work with 2FA

[theAkito]

• Gitea version (or commit ref): b84a251fc
• Git version: 2.11.0
• Operating system: DietPi (based on Raspbian Stretch)
• Database (use [x]):
  
  
  
  • [x] PostgreSQL
  
  
  • [ ] MySQL
  
  
  • [ ] MSSQL
  
  
  • [ ] SQLite
  
  
• Can you reproduce the bug at https://try.gitea.io:
  
  
  
  • [ ] Yes (provide example URL)
  
  
  • [ ] No
  
  
  • [x] Not relevant
  
  
• Log gist: x

Description

I want to clone (migrate) a public repository from Github to my account. I don't want to migrate any Issues, Wikis or anything. Just the repository. Every time I try to do that, it tells me I have to put in my credentials (I should not have to). If I put in my credentials, it still does not work, because it does not accept 2FA.

[lunny]

Are you migrating a private repository?

[theAkito]

Are you migrating a private repository?

No, absolutely not. Else I would not have access to it myself. 😄

[mrsdizzie]

You should be able to use a personal access token for this:

At github go to https://github.com/settings/tokens and create one then you can use that token as the username on the migration form

[theAkito]

You should be able to use a personal access token for this:

At github go to https://github.com/settings/tokens and create one then you can use that token as the username on the migration form

Well, even if I can do it after setting the token, this does not solve the root cause, yet. The root cause is that I have to put in credentials, at all, to be able to access a public repository. I shouldn't have to set any token or put in any credentials, in the first place.

[mrsdizzie]

Unauthenticated requests are very limited by Github API and would fail for many migrations

[theAkito]

Unauthenticated requests are very limited by Github API and would fail for many migrations

Every migration that happened before the update that added the feature to migrate more than just the repository was successful. That said, if it was hard to (lite) fork a clean repository, then it would be also hard to clone the repository. The server basically just has to clone the repository.

[zeripath]

It's not just a clone of a repository over git anymore, we're getting things like issues - stuff which has to be obtained over the API.

[theAkito]

It's not just a clone of a repository over git anymore, we're getting things like issues - stuff which has to be obtained over the API.

That is what I am addressing. I do not want to migrate any issues or anything like that. I just want to have a clean repository. That's it. No need for any API whatsoever. Just git clone https://github.com/user/myrepo. That's it.

[mrsdizzie]

Yes you can still enter no authentication information and have the repo cloned as normal without any issues, pr, etc from Github just as it was before.

Just put in the address of the repo and leave username/password blank

[theAkito]

Yes you can still enter no authentication information and have the repo cloned as normal without any issues, pr, etc from Github just as it was before.

Just put in the address of the repo and leave username/password blank

Please read the OP before commenting.

[jolheiser]

I just successfully cloned a repo on try with no user/pass. I was also able to migrate using my personal instance running 1.9.0
https://try.gitea.io/jolheiser/athens

Can you reproduce on try?

[theAkito]

I just successfully cloned a repo on try with no user/pass.
https://try.gitea.io/jolheiser/athens

Can you reproduce on try?

I do have a very new version of Gitea, but it is not the absolutely newest. Should I update? I did not do it yet, because I didn't think that those couple of days would've already implied a fix.

[mrsdizzie]

Can you provide an example of a public Github repo that doesn't work and requires authentication?

[theAkito]

Can you provide an example of a public Github repo that doesn't work and requires authentication?

Ironically, when I wanted to clone the repository I wanted to save it from being deleted or lost, because of controversies regarding this repository. Now, I did not get to migrate the repository because of this Gitea bug and well what do you know, I can't find the repository anymore and it might be lost. What a failure.

[lunny]

Migrating public git repository has been released since gitea forked from gogs and I have used that feature over 200 times. Haven't found that issue.

[theAkito]

Migrating public git repository has been released since gitea forked from gogs and I have used that feature over 200 times. Haven't found that issue.

Same. Until the new feature came in, where you could also migrate issues, etc.

[jolheiser]

I created a local build at the specified commit (b84a251) and was able to successfully clone public GitHub repositories with no credentials.

I'm sorry this happened to you, however I don't know where else to look since I cannot reproduce it. If you are able to reproduce it in the future, please let us know so we can track down any potential bug.

[theAkito]

I created a local build at the specified commit (b84a251) and was able to successfully clone public GitHub repositories with no credentials.

I'm sorry this happened to you, however I don't know where else to look since I cannot reproduce it. If you are able to reproduce it in the future, please let us know so we can track down any potential bug.

I found an example:
https://github.com/TakmingMark/Plumble-1.git

Whenever I try to clone this, I get this

Authentication failed: GET https://api.github.com/repos/TakmingMark/Plumble-1: 401 Bad credentials []

I didn't even put in my username or password, at all. I also didn't select to migrate issues or anything like that.

[jolheiser]

Is your browser filling in credentials for some reason?
I can migrate/clone that repo successfully on both try as well as my local build with no credentials.

[sapk]

How do you run gitea ? Via docker? From your running user ?
I suspect that you may have a global or user git config that may alter the request.

[theAkito]

Is your browser filling in credentials for some reason?
I can migrate/clone that repo successfully on both try as well as my local build with no credentials.

Well.
I didn't know it even fills in hidden entries. I purposefully never opened it to not even let it think about filling in anything. This seemed to be it. Sorry about all the fuzz.

[mjanssens]

Glad I found this issue, my username was filled in automatically, but the credentials fields weren't visible by default.
Perhaps it would be better to give a regular user more specific feedback about the issue. Feedback is indeed in the log as "401 bad credentials". But in the web interface, the only message is " failed".