Fin ChristensenJan 23, 2020

@paolo @rugk Oh no, I misunderstood the migration form 🙈 I thought the `Migrate` label indicates the form field for the github username...

Sadly, the gitea FAQ points to the gitea-github-migrator tool which lead me in the wrong direction:
https://docs.gitea.io/en-us/faq/#how-to-migrate-from-gogs-github-etc-to-gitea

FAQ - Docs

Show threadFin ChristensenJan 23, 2020

@paolo @rugk Also, Github informed me that using a password-based authentication for migration is deprecated:

> You recently used a password to access an endpoint through the GitHub API using go-github. We will deprecate basic authentication using password to this endpoint soon:
> We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.

Build software better, together

GitHub is where people build software. More than 65 million people use GitHub to discover, fork, and contribute to over 200 million projects.

Show threadFin ChristensenJan 23, 2020
@paolo @rugk Changing the password label to something like `API Token` and providing the above link to generate such a token would help users. I tested the migration with a PAT and it worked flawlessly.
Show threadrugk OLD ACCOUNT
@fin_ger
So? Send PR/MRs?
@paolo
Jan 23, 2020 at 1:13pmWeb
Show threadFin ChristensenJan 23, 2020

@rugk @paolo I submitted some issues

https://github.com/go-gitea/gitea/issues/7635
https://github.com/go-gitea/gitea/issues/9951

New Migration interface improvements · Issue #7635 · go-gitea/gitea

When doing a migration, it doesn't show the options to migrate issues,pr,etc.. until you put in authentication information which is confusing and leads people to think those aren't availabl...