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

sl pr submit picking upstream over fork is unexpected and not desired #991

Open
chipsenkbeil opened this issue Nov 29, 2024 · 0 comments
Open

Comments

@chipsenkbeil
Copy link

I made the mistake of sending a massive number of pull requests to the neovim repository, thinking that sl pr submit --stack would use my fork. I then read through the documentation to realize that it prefers the upstream repository in the case where default or default-push are a fork, which is not the behavior I'd expect.

It's not clear to me how to control this behavior other than not using a forked repository and instead manually cloning the repository using git and pushing to my own version without the fork. As the upstream repository does not want multiple pull requests due to the load on the CI, I was planning to have a dialog on my fork and merge all of the work into a single PR down the line.

Is there any guidance on how to get Sapling's pr submit to go to a fork?

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

1 participant