Why Github takes priority to show Merge location instead of What actually has been done in the merge

Below you can see a common example "Merge <type> from <location> "

 Why information about how the changes has been made are more important, than what changes were actually commited, more important than the description why it was merged.

The description should be at the top.
And then if there is need to check where it came from - expand on more information after clicking […] button.
It is common sense, why this was even decided to be used in github other way?

This post was moved to a different board that fits your topic of discussion a bit better. This means you’ll get better engagement on your post, and it keeps our Community organized so users can more easily find information.

As you’ll notice, your Topic is now in the How to use Git and GitHub board. No action is needed on your part; you can continue the conversation as normal here.

1 Like

Hi @boqsc,

Thanks for the feedback! We’re always working to improve GitHub, and we consider every suggestion we receive. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.

Please let me know if you have any other questions.

Cheers!

1 Like