-
Notifications
You must be signed in to change notification settings - Fork 10
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
Comments
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. |
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:
I hope this helps! |
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?
The text was updated successfully, but these errors were encountered: