When pushing to a remote, it seems preferable, if the branch is pushed to a branch with the same name in the remote repository by default.\r+
According to the help message, it should be that way:\r +
--to-branch <remote_branch> The branch to push into. Defaults to the current branch.\r +
But instead it will be pushed to the remote master branch when not specified differently.\r +
--to-branch <remote_branch> The branch to push into. Defaults to the current branch.
Relatedly: it might also be helpful to indicate which branch is being pushed to in the UI, so that users are less likely to push to the wrong branch.
Patches incoming!\r +
This patch makes pijul push push to the current branch instead of the master branch by default.\r +
This patch addresses AveryLychee's comment by displaying the branch being pushed to.
Thanks a lot for your submission! I will try to have a look at that as soon as possible.\r +
In practice, your changes seems logical and valuable, I only fear that pijul commands are getting more and more arguments without any high-level conception, which means we might eventually fall into the very same hole git fell into years ago.
The "more feedback" patch looks good to me! @lthms, I do see your point for the other one, not for this one. Let's talk about the "fork without switching" in discussion #369.
Ok, I just applied the "more feedback" patch. I like the other idea (pushing to a branch with the same name), and it is completely feasible (by calling pijul branches on the remote, if there is no default remote branch for the current branch), so I'll leave this discussion open.