Replies: 2 comments 1 reply
-
@tarsius bump. There are maintainer-directed questions in here. I have some memory of getting an answer to these at one point, but I must be mistaken, because I don't see an answer here. If I'm not mistaken, sorry for the noise. Thanks |
Beta Was this translation helpful? Give feedback.
-
Try the "merge into" variant. That checks out the upstream branch and then merges and deletes the feature branch.
It seems okay that you have to do 4 explicitly. |
Beta Was this translation helpful? Give feedback.
-
There are sequences of commands I find myself running all the time, and I wonder if these kinds of things should somehow be bundled into Magit features. For example,
I just finished work on a branch. It was merged. I'm still on that branch. Now I want to:
Every time I go through this I think, “this is the sort of thing that Magit usually makes less tedious.” Would something like that be in scope?
Another: I want to submit a PR fixing a particular thing I found in
main
.Another: I want to submit a PR with the work I've done:
Another: I've just made a one-commit change on main. I want to spin off a branch with a name derived from the first line of the commit message, push it to the default upstream, and create a PR.
Another: I've made that change but haven't committed it yet. I want it to prompt me for the commit message and do all of the above (same command)
Would these kinds of things be in scope for Magit?
Beta Was this translation helpful? Give feedback.
All reactions