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

Make it a fork on GitHub #9

Closed
antoyo opened this issue May 23, 2024 · 2 comments
Closed

Make it a fork on GitHub #9

antoyo opened this issue May 23, 2024 · 2 comments
Labels
question Further information is requested

Comments

@antoyo
Copy link

antoyo commented May 23, 2024

Hi.
Any reason why this doesn't show as a fork of helix on GitHub?
I would find this useful to compare with the original helix.
Thanks.

@usagi-flow
Copy link
Owner

Unfortunately, there is a very specific reason indeed. Moreover, this repository used to be an actual GitHub fork until last week, where I submitted a support ticket to have this repository "detached".

In a forked repository, when you create a PR, GitHub by default selects the default branch of the upstream repository as the base branch, and thinks you want to create a PR in the upstream repository. This is very annoying and error-prone when you want to merge changes which aren't meant to be submitted to upstream (e.g. Vim keybindings).

There is no known setting to configure this, there's a lot of people wanting such a setting, and it doesn't seem like GitHub cares much about it: https://github.com/orgs/community/discussions/11729

I wish we could combine the best of two worlds, but that decision lies in GitHub's hands, unfortunately.
I'm open to any suggestions, that said.

@usagi-flow usagi-flow closed this as not planned Won't fix, can't repro, duplicate, stale May 24, 2024
@antoyo
Copy link
Author

antoyo commented May 24, 2024

I completely understand since I have the same problems on one of my projects.
Let's hope it's going to be fixed eventually.

@usagi-flow usagi-flow added the question Further information is requested label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants