Option to push branch into a specific remote #480

Activity

1. mislav commented on Feb 17, 2020

   

   mislav

   on Feb 17, 2020

   Contributor

   More actions

   Thanks for writing in!

   currently when you open a pr from a branch, it's pushed into the repo it's originated from.

   We only push to the origin repo if you have write access to it in the first place. Is there a use-case where you have write access to the origin repo, but you still don't want to push there?

   Also, does this push fail for you right now?

   this would fit lots of the workflows in lots of opensource projects when you don't have write-access to the main repo.

   When you don't have write access to the main repo, we fork it and push to your fork instead. This all happens by default. If you do not experience that this works, can you tell us more about your setup and paste some error messages?
2. mislav

   added

   more-info-neededMore info needed from user/contributorMore info needed from user/contributor

   on Feb 17, 2020
3. fruch commented on Feb 17, 2020

   

   fruch

   on Feb 17, 2020

   Author

   More actions

   I have a fork already, and I have write access to both.

   $ git remote -v
   origin  [email protected]:fruch/scylla-cluster-tests.git (fetch)
   origin  [email protected]:fruch/scylla-cluster-tests.git (push)
   upstream        [email protected]:scylladb/scylla-cluster-tests.git (fetch)
   upstream        [email protected]:scylladb/scylla-cluster-tests.git (push)
   

   origin is my fork

   when I've used gh pr create from a branch created from upstream/master, the branch was pushed to upstream and not into origin as I would like to.
4. fruch commented on Feb 17, 2020

   

   fruch

   on Feb 17, 2020

   Author

   More actions

   Some more info, pushing into the upstream in my case, trigger more CI build which. the work flow of the whole team is to work on your own fork.

   I've run into it, since after creating the PR, I've pushed updated to my own fork, and not seeing them in the PR.

   maybe my workflow is a bit weird or backwards, but it would be nice to have a bit more control when needed.
5. mislav commented on Feb 17, 2020

   

   mislav

   on Feb 17, 2020

   Contributor

   More actions

   maybe my workflow is a bit weird or backwards, but it would be nice to have a bit more control when needed.

   Your workflow doesn't seem weird at all; thanks for clarifying.

   I will close this as duplicate of #350 where people have been requesting the option to indicate their preference that they want to always push to a fork instead of to upstream, even if they have write access.
6. mislav

   closed this as completedon Feb 17, 2020
7. casperdcl commented on Mar 17, 2020

   

   casperdcl

   on Mar 17, 2020

   Last edited by casperdcl

   More actions

   This isn't a duplicate of #350. #350 is about changing defaults. This (#480) is about exposing an option:

   gh pr create --remote myuser/myfork
8. mislav commented on Mar 17, 2020

   

   mislav

   on Mar 17, 2020

   Last edited by mislav

   Contributor

   More actions

   @casperdcl I understand that this is not an exact duplicate, but in the referenced thread we're discussing a better default for where the branch is pushed, plus we're planning to respect if the branch is already pushed to a specific remote. The combination of those two improvements should make a vast improvement in experience for our users:

   1. gh pr create by default will always push to a fork if one exists - this will be a better default since the considerable majority of users have asked for this. A better default (ideally) means that fewer people will need an option to change it.
   2. git push <remote> HEAD && gh pr create will allow one to choose where the branch is pushed, alleviating the need for --remote flag.

   At this moment we're trying to avoid adding too many configuration flags because that could over time prove to be difficult to maintain.
9. casperdcl commented on Mar 17, 2020

   

   casperdcl

   on Mar 17, 2020

   More actions

   on the other hand, quietly setting defaults without exposing config options is also dangerous. I don't personally mind, but others might. Happy if (2) works:

   git checkout upstream/master
   git checkout -b <branch>
   git push -u <fork> <branch>
   gh pr create

   will auto-create a PR fork:branch -> upstream:master

   👍React with 👍1Reacted by Mislav Marohnić
10. fruch commented on Sep 5, 2024

    

    fruch

    on Sep 5, 2024

    Author

    More actions

    I'm run into this issue today, and surprisingly someone already suggested here what I need in 2020... thanks @fruch you know exactly what I need...

    just to add to who here, this option does exist now

    gh create ... --head origin:branch_name
11. Stonre

    added a commit that references this issue on Jul 21, 2025

    build(pyproject): update development status classifier (cli#480)

    6638fb0