Feature suggestion: Use ${src_org}-pages as the default name when forking a pages repo #593

Open

opened 3 months ago by hexagon-recursion-poc0 · 1 comments

hexagon-recursion-poc0 commented 3 months ago

Imagine

Alice wants to contribute to https://fdroidfamily.codeberg.page
Alice signs up on codeberg.org
Alice forks https://codeberg.org/fdroidfamily/pages
The default name for her fork is https://codeberg.org/alice/pages. She does not edit the name when forking because she does not realize the implications. She did not read the fine manual
Now https://alice.codeberg.page is a mirror of https://fdroidfamily.codeberg.page which is not what Alice intended

Suggested improvement

It would be more user friendly if the default name when cloning a pages repository was "https://codeberg.org/alice/fdroidfamily-pages"

fnetX commented 3 months ago

Collaborator

Does such behaviour also makes sense for every other repo? While forking a unique project name, keeping the repo name only might be desirable (e.g. go-gitea/gitea → gitea), but when forking projects with generic names from other people (e.g. their "dotfiles", "website", or some "blog", it might be better to turn them into user1-dotfiles, project2-website or codeberg-blog).

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.