[Bug] UpdateMigrationsByType only executed if you link an account #5267

New Issue

GiteaMirror · 2025-11-02T06:19:40-06:00

GiteaMirror commented

2025-11-02 06:19:40 -06:00

Originally created by @6543 on GitHub (Apr 20, 2020).

since v1.11

if you login via github and creat a new account instead of linking to one migrated issues from github are not migrated to the new account.

to reproduce:

Migrate a repo with issues from github witch contain issues of a (not jet on gitea created test user)
login with test-user via github and creat new account
look at migrated issues the test user dont own them :/

workaround:
creat a local gitea account first and link to github second

Originally created by @6543 on GitHub (Apr 20, 2020). since v1.11 if you login via github and creat a new account instead of linking to one migrated issues from github are not migrated to the new account. to reproduce: 1. Migrate a repo with issues from github witch contain issues of a (not jet on gitea created test user) 2. login with test-user via github and creat new account 3. look at migrated issues the test user dont own them :/ workaround: creat a local gitea account first and link to github second

GiteaMirror added the issue/confirmed label 2025-11-02 06:19:40 -06:00

GiteaMirror commented

2025-11-02 06:19:41 -06:00

@guillep2k commented on GitHub (Apr 21, 2020):

I think the idea is to avoid storing raw credentials.

@guillep2k commented on GitHub (Apr 21, 2020): I think the idea is to avoid storing raw credentials.

GiteaMirror commented

2025-11-02 06:19:41 -06:00

@zeripath commented on GitHub (May 14, 2020):

So @6543 are you able to duplicate this easily?

If so it would be useful to add logging in to:

1982194dc5/routers/user/auth.go (L668-L713)

to figure out what kind of user is returned.

Then we can look at:

1982194dc5/routers/user/auth.go (L589-L666)

@zeripath commented on GitHub (May 14, 2020): So @6543 are you able to duplicate this easily? If so it would be useful to add logging in to: https://github.com/go-gitea/gitea/blob/1982194dc5abe1b400245414bac09f83957b4fe5/routers/user/auth.go#L668-L713 to figure out what kind of user is returned. Then we can look at: https://github.com/go-gitea/gitea/blob/1982194dc5abe1b400245414bac09f83957b4fe5/routers/user/auth.go#L589-L666

GiteaMirror commented

2025-11-02 06:19:41 -06:00

@lunny commented on GitHub (May 17, 2020):

@6543 so next time you login with github account, it will migrated too?

@lunny commented on GitHub (May 17, 2020): @6543 so next time you login with github account, it will migrated too?

GiteaMirror commented

2025-11-02 06:19:41 -06:00

@stale[bot] commented on GitHub (Jul 18, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jul 18, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:19:42 -06:00

@6543 commented on GitHub (Jul 18, 2020):

the savest way is to add a "Run Migration" button to the user settings so a user can manualy alwas take over there issues&pulls

@6543 commented on GitHub (Jul 18, 2020): the savest way is to add a "Run Migration" button to the user settings so a user can manualy alwas take over there issues&pulls

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5267