Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rehome this repo? #70

Open
nlharris opened this issue Jan 11, 2022 · 2 comments
Open

Rehome this repo? #70

nlharris opened this issue Jan 11, 2022 · 2 comments

Comments

@nlharris
Copy link
Member

Why is this repo still a fork from kushinauwu/OBF-Homepage-New? Shouldn't it live directly in the OBF org? I don't know how to move it. If we did move it, would we lose history?

@hlapp
Copy link
Member

hlapp commented Jan 11, 2022

It does live directly in the OBF org. The fact that it is a fork (which really only means that it started as one) is merely some meta-information that GitHub keeps around in order to change and tailor certain behaviors (in particular for pull requests) from their defaults for repos that didn't start as a fork.

Now, arguably, those changes in default behavior for pull requests are neither desirable or useful anymore here, because there is no intent to keep up this fork with the upstream repo; in fact, what would normally be referred to as "upstream" is in our case simply a now-unmaintained repository that at some point we cloned this one from. So I would agree with what is probably your real question, namely can we please remove the metadata fact that this is a fork so that pull request behavior reverts to the default for "non-forked" repos.

However, GitHub does not allow one to "clear" the "this is a fork" status. The way to achieve this would be to create a local backup the repo, then recreate one from the backup. This could risk losing the issue and pull request tracker history, though.

@erik-whiting
Copy link

According to this how-to article, "unforking" can be done via a chatbot. I'll copy and paste the steps from that page for convenience:

  1. Go to support.github.com/request (or go to github.com and click Contact GitHub in the footer).

  2. Click Attach, detach or reroute forks.

  3. In the Subject field, typ 'Unfork'. A blue banner should appear with 'Our virtual assistant can help'. Click the banner.

  4. A chat should appear on screen with the Virtual Assistant. Paste the URL of the repository.
    _Note: make sure to paste the URL to the forked repository, so not the original repository. It should look like github.com/username/forked-repo-name.

  5. Specify what should be done with Child forks:

    If username/forked-repo-name has child forks, what should we do with these?
    Commonly you'll want to bring the child forks along with you when detaching your fork from the upstream repository.

    1. Bring the child forks with the repository
    2. Leave the child forks behind

    Select one of the options and send the form.

  6. Within a few minutes to half an hour you should get a confirmation in your e-mail.

Now you've successfully unforked a GitHub repository! The repository stays in your account as a personal repository, without ties to the original repository.

I hope this helps!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants