[🍴] Unable to fork a forked repo #732

Open
opened 2 weeks ago by a9 · 2 comments
a9 commented 2 weeks ago

Hard to explain but I can't seem to create a fork of a forked repo because I have a fork of the original repo that it's based from.

I want to fork [3].

When I try to fork [3] I just get sent back to my old fork [2] even though the repo name I set is different than my old repo.

It's the first time I've encountered this so I'm not entirely sure if it's just how forking works or if it's a bug. If deleting [2] is the only way to get [3] in my account then I'll just do that.


fork fork fork fork fork 🍴

<!-- NOTE: If your issue is a security concern, please send an email to contact@codeberg.org (and if related to Gitea also to security@gitea.io) instead of opening a public issue. Thank you. Welcome to the Codeberg Community Tracker. This is the right place for bug reports, feature requests and feedback. It's the central place where we track progress and discuss, so please open issues here unless you are sure it's directly related to a specific Codeberg product and only some contributors there need to join the discussion. Easy rule: If you are unsure, report it here. When reporting bugs or asking for features in the software itself, please understand that Codeberg is a fork of Gitea. Please always check upstream (→ see FAQ) if your there is already an open issue. If not, you'd really help us if you could directly get in touch with the maintainers and open an issue here if you think a wider audience should know about that (e. g. when discussing hotfixes, backports or when discussing whether some feature should become part of Gitea or a Codeberg "add-on"). If you don't have a GitHub account, please mention this and we'll gladly forward your report to the Gitea maintainers. Thank you for reporting your findings and giving feedback on Codeberg. ## Some FAQ: ### What does upstream mean? Upstream refers to Gitea, the software Codeberg is built upon. If we ask you if you can report upstream, please visit https://github.com/go-gitea/gitea/issues and check for the bug there and report elsewise. It's usually good if the person interested in a feature or bugfix opens the request to react to questions and join the discussion. We would usually just fire the report, but won't find the time to properly react to that ... **If you do not have a GitHub account**, just tell us and we'll happily forward the report for you. ### I just noticed a typo in the sign_up / sing_up route when regis... No, this is not a typo, but intentional. It was a quick fix to avoid spammers targetting our instance and it actually worked out quite well to rename the route from sign_up to sing_up (few people notice, nice to see you have sharp eyes) ... we might have to take more effective countermeasures in the future, but for now we're actually quite good with that one ... ### How can I help? If you want to help improving Codeberg as a community home for software development, we'll gladly welcome your contribution. Check out the docs about improving Codeberg https://docs.codeberg.org/improving-codeberg/ and have a look at the open issues, especially those that are looking for contribution https://codeberg.org/Codeberg/Community/issues?state=open&labels=105 - some of them don't even require much coding knowledge. We are also happy if you forward bug reports to Gitea if the original author hasn't done that yet or hasn't got a GitHub account. --> Hard to explain but I can't seem to create a fork of a forked repo because I have a fork of the original repo that it's based from. - [1] Original Repo: https://codeberg.org/3np/rimgu - [2] My Fork of Original: https://codeberg.org/a9/rimgu - [3] Forked Original Repo (Go rewrite): https://codeberg.org/video-prize-ranch/rimgo I want to fork [3]. When I try to fork [3] I just get sent back to my old fork [2] even though the repo name I set is different than my old repo. It's the first time I've encountered this so I'm not entirely sure if it's just how forking works or if it's a bug. If deleting [2] is the only way to get [3] in my account then I'll just do that. --- fork fork fork fork fork 🍴

I Think forking another fork of the same repository should not resut in douplicating it. Instead you should simply add another origin to your first and one and only fork of that repo.

git remote add https://codeberg.org/video-prize-ranch/rimgo

Maybe this needs to be done locally on your laptop. YOu then can create a branch of the commits relevant to you and then you can push that to the/your (one and only) fork on codeberg.

I Think forking another fork of the same repository should not resut in douplicating it. Instead you should simply add another origin to your first and one and only fork of that repo. <pre> git remote add https://codeberg.org/video-prize-ranch/rimgo </pre> Maybe this needs to be done locally on your laptop. YOu then can create a branch of the commits relevant to you and then you can push that to the/your (one and only) fork on codeberg.
rwa added the
gitea-related
label 2 weeks ago
Collaborator

This might be related:
https://github.com/go-gitea/gitea/issues/20229

I think the main issue is that - although https://codeberg.org/video-prize-ranch/rimgo is forked from the original repo - it is a completely different software by now.

If you don't want to loose the commits in your forked repo https://codeberg.org/a9/rimgu, you can try to remove the fork relationship under "Settings -> Convert to Regular Repository".
You should be able to fork https://codeberg.org/video-prize-ranch/rimgo afterwards.

This might be related: https://github.com/go-gitea/gitea/issues/20229 I think the main issue is that - although https://codeberg.org/video-prize-ranch/rimgo is forked from the original repo - it is a completely different software by now. If you don't want to loose the commits in your forked repo https://codeberg.org/a9/rimgu, you can try to remove the fork relationship under "Settings -> Convert to Regular Repository". You should be able to fork https://codeberg.org/video-prize-ranch/rimgo afterwards.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Codeberg/Community#732
Loading…
There is no content yet.