New Migration interface improvements #3683

New Issue

GiteaMirror · 2025-11-02T05:21:37-06:00

GiteaMirror commented

2025-11-02 05:21:37 -06:00

Originally created by @mrsdizzie on GitHub (Jul 26, 2019).

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 available before even trying.

I think it should always show the checkboxes and perhaps just grey them out until information has been added (with text indicating why).

Also I think we should make it clear that you can add a token in the username field which is a very nice but also unknown feature for migration.

This would be nice to have for 1.9 since migration is new for this release and it would give a better first impression (and should be just a small ui change)

Originally created by @mrsdizzie on GitHub (Jul 26, 2019). 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 available before even trying. I think it should always show the checkboxes and perhaps just grey them out until information has been added (with text indicating why). Also I think we should make it clear that you can add a token in the username field which is a very nice but also unknown feature for migration. This would be nice to have for 1.9 since migration is new for this release and it would give a better first impression (and should be just a small ui change)

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 05:21:37 -06:00

GiteaMirror closed this issue

2025-11-02 05:21:37 -06:00

GiteaMirror commented

2025-11-02 05:21:38 -06:00

@stale[bot] commented on GitHub (Sep 25, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 25, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:21:38 -06:00

@fin-ger commented on GitHub (Jan 23, 2020):

I ran into exactly this problem. Also, the password based authentication for the github API seems to be deprecated. So, for github migrations, the migration form should always ask for a Personal Access Token.

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.
-- Email from github

@fin-ger commented on GitHub (Jan 23, 2020): I ran into exactly this problem. Also, the password based authentication for the github API seems to be deprecated. So, for github migrations, the migration form should always ask for a Personal Access Token. > 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. > -- Email from github

GiteaMirror commented

2025-11-02 05:21:38 -06:00

@TheTechRobo commented on GitHub (May 31, 2020):

This would be incredibly useful. I spent about an hour looking for how to migrate issues, PRs, etc.

@TheTechRobo commented on GitHub (May 31, 2020): This would be incredibly useful. I spent about an hour looking for how to migrate issues, PRs, etc.

GiteaMirror commented

2025-11-02 05:21:38 -06:00

@lunny commented on GitHub (Jun 1, 2020):

We can add a middle page before current migration page. It will let you chose migration type, if you chose non-git, issues/pulls/releases ... will be displayed on the next page. If you chose git, the options will not be displayed.

@lunny commented on GitHub (Jun 1, 2020): We can add a middle page before current migration page. It will let you chose migration type, if you chose non-git, issues/pulls/releases ... will be displayed on the next page. If you chose git, the options will not be displayed. <img width="181" alt="图片" src="https://user-images.githubusercontent.com/81045/83367056-29106500-a3e5-11ea-8be1-09bbe1db66a2.png">

GiteaMirror commented

2025-11-02 05:21:38 -06:00

@mrsdizzie commented on GitHub (Jun 1, 2020):

@lunny only if we can use that drawing as the interface ; )

@mrsdizzie commented on GitHub (Jun 1, 2020): @lunny only if we can use that drawing as the interface ; )

GiteaMirror commented

2025-11-02 05:21:38 -06:00

@lunny commented on GitHub (Jul 7, 2020):

@mrsdizzie any idea? I will try to send a PR to do that.

@lunny commented on GitHub (Jul 7, 2020): @mrsdizzie any idea? I will try to send a PR to do that.

GiteaMirror commented

2025-11-02 05:21:39 -06:00

@jolheiser commented on GitHub (Aug 31, 2020):

Fixed by #12619

@jolheiser commented on GitHub (Aug 31, 2020): Fixed by #12619

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#3683