#199 Possible Improvements for New Migration (from github)

Open
opened 2 weeks ago by wolframkriesing · 5 comments

First things first, thanks a lot for codeberg. Great work.

Context: I migrated a project from github using “New Migration” page. I came across some things I did not understand.
I looked up help before writing this ticket. I looked up gitea docs first, I did not yet look up the codeberg source code.
Note: I am picky on words and it might feels annoying, I am not trying to annoy at all, I want to help improving codeberg for everyone. I believe the better the wording and describing the better the UX and the more fun for everyone.

Problem:

  1. On the “New Migration” page it says When migrating from github, input a username and migration options will be displayed.. Does this mean I should enter the username under “Clone Authorization” below? If so, maybe some wording like ...input your github credentials under "Clone Authorization" and ... would make that easier to understand?
  2. I did not understand what “Clone Authorization” means. Are those the crecentials for github I enter here?
  3. If “Clone Authorization” means my github credentials, I am not sure if this is a good idea from a security point of view. It does not feel right to enter my credentials here. Maybe asking for an github access token is a better idea?
  4. It says “migration options will be displayed” I assume I need to enter something under “Clone Authorization” for that, right?

Thanks and keep up the good work!

First things first, thanks a lot for codeberg. Great work. **Context**: I migrated a project from github using ["New Migration"](https://codeberg.org/repo/migrate) page. I came across some things I did not understand. I looked up help before writing this ticket. I looked up gitea docs first, I did not yet look up the codeberg source code. Note: I am picky on words and it might feels annoying, I am not trying to annoy at all, I want to help improving codeberg for everyone. I believe the better the wording and describing the better the UX and the more fun for everyone. **Problem**: 1) On the "New Migration" page it says `When migrating from github, input a username and migration options will be displayed.`. Does this mean I should enter the username under "Clone Authorization" below? If so, maybe some wording like `...input your github credentials under "Clone Authorization" and ...` would make that easier to understand? 2) I did not understand what "Clone Authorization" means. Are those the crecentials for github I enter here? 3) If "Clone Authorization" means my github credentials, I am not sure if this is a good idea from a security point of view. It does not feel right to enter my credentials here. Maybe asking for an github access token is a better idea? 4) It says "migration options will be displayed" I assume I need to enter something under "Clone Authorization" for that, right? Thanks and keep up the good work!
6543 commented 2 weeks ago

@wolframkriesing you have to instert a github url into “Migrate / Clone From URL” and the username in “Clone Authorization” now the options are displayed - if you like to use a token just put it instead the username and leafe password field blank

and yes I agree this need an impruvement.

@wolframkriesing you have to instert a github url into "Migrate / Clone From URL" and the username in "Clone Authorization" now the options are displayed - if you like to use a token just put it instead the username and leafe password field blank and yes I agree this need an impruvement.
wolframkriesing commented 2 weeks ago
Poster

Thanks for the explanation. Indeed.
I tried migrating the next repo now I saw it. Alright.
I would not have expected the migration options to show up when I enter a username, is the username in the clone-URL above not enough? I am not sure of the purpose of the username.

Thanks for the explanation. Indeed. I tried migrating the next repo now I saw it. Alright. I would not have expected the migration options to show up when I enter a username, is the username in the clone-URL above not enough? I am not sure of the purpose of the username.
wolframkriesing commented 2 weeks ago
Poster

I just had entered my username in the “Clone Authorization” but the migration failed, I tried it multiple times. Without the username in there it worked. (this repo https://codeberg.org/wolframkriesing/hamjest-spy in case it matters)

I just had entered my username in the "Clone Authorization" but the migration failed, I tried it multiple times. Without the username in there it worked. (this repo https://codeberg.org/wolframkriesing/hamjest-spy in case it matters)
ashimokawa commented 2 weeks ago
Owner

@wolframkriesing

You do not have to enter credentials if you just want to migrate the a itself. But if you want issues, comments, PRs etc you have to. We do not save them on codeberg.

If I remember correctly I entered my username and as password an access token and it worked when I migrated.

username and username in clone url are not redundant because it is possible to migrate the repository of someone else...

@wolframkriesing You do not have to enter credentials if you just want to migrate the a itself. But if you want issues, comments, PRs etc you have to. We do not save them on codeberg. If I remember correctly I entered my username and as password an access token and it worked when I migrated. username and username in clone url are not redundant because it is possible to migrate the repository of someone else...
wolframkriesing commented 2 weeks ago
Poster

true, migrating a repo with a different username is something I didnt think of. thanks

true, migrating a repo with a different username is something I didnt think of. thanks
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.