Hacker News new | ask | show | jobs
by happypeter 4885 days ago
In my daily workflow, a feature branch is there on the server mostly for it's part of a already-sent pull request. So in this case, do a syncing does not make any sense.

For a feature branch from my local clone, I do love to sync with upstream/master as often as I can, but I can do it quickly and knowingly(rebase or merge) with command line.

So for me, thanks but no thanks.

But I do know a lot people use the remote feature branch as a tmp backup of the WIP feather branch, in this case, the fact that you can quickly sync with upstream/master does help, but what if you click "sync branch" and merge conflicts happen?

1 comments

I'm a bit green to the workflow my self, but I agree with you, this doesn't seem to add anything.

Why is having the server doing the merge advantageous to doing the merge locally?

From the blog post: without ever needing to go to the command line. So I think their goal is to make things even easier for users that have trouble (or don't like) the command line.