Feature suggestion: Use ${src_org}-pages as the default name when forking a pages repo #593
Labels
No Label
bug
Codeberg
contribution welcome
docs
duplicate
enhancement
infrastructure
legal
licence / ToS
public relations
question
s/Gitea/Forgejo
s/Pages
s/Weblate
s/Woodpecker
security
service
spam
upstream
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Codeberg/Community#593
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Imagine
Suggested improvement
It would be more user friendly if the default name when cloning a pages repository was "https://codeberg.org/alice/fdroidfamily-pages"
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).
that's a UX suggestion ... I'm personaly not sure if we should add it :/
I think this generally makes a lot of sense to add (fork codeberg/docs to user/codeberg-docs instead of "docs", which might already have been forked from project-xyz/docs)