Hacker News new | ask | show | jobs
by shiv86 2052 days ago
It is completely non-intuitive UX which is causing a lot of people issues. Merging branches is the bread and butter of GIT, if you are changing a fundamental primitive (mergers) of how a technology is expected to work, by reversing the direction of the merge request (opposite to the direction provided explicitly by the user) without warning that is a major issue.
1 comments
wiml 2052 days ago
It's not really messing with anything fundamental about Git — in fact it's providing a very common workflow for Git users, just in a way that is confusing for people who mainly use Github.

Obviously if lots of people are getting confused something needs to be fixed, but I think this is fundamentally a minor UI wart.

link
shiv86 2045 days ago
> just in a way that is confusing for people who mainly use Github.

As a user I am requesting to merge branch X into branch Y. What Github actually does is merge branch Y into branch W, with insufficient warning to the user. Gitlab users continue to have issues due to this unexpected behavior. I am astounded this problem has not been addressed in a meaningful way, so users dont counter this issue.

link