New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore functionality from sync-pr-commit-title
removed in #2738
#2768
Comments
I removed it because merge commits are indistinguishable, so in a list it looks like that commit added a feature and then the following commits did the same. If the merge commit title is the default (Merge X into Y) then it’s more clear I think it you want to keep each commit in history it’s best to rebase them. Can you show me an example of a merge commit you made? |
Well my commits previously looked like this:
I feel that the whole But perhaps you are right it may not make much sense to other people. |
I personally think merge commits are just noise in most cases, so I may not be the right person to talk about them. In that example I just don’t see it being an advantage over the current situation. I’d perhaps suggest we restore an old feature that made merge commits distinguishable (and if I remember correctly also dimmed them). We dropped it because there’s no “merge commit class” in the DOM anymore, so we could instead detect them if their title starts with |
I personally really liked the merge renaming when it was done like that: I do agree with @fregante that merge commits are kinda noisy, but not every org or team is able to have squash merge as a default. Or maybe users should be given the option to choose if they care about distinguishing? Although I guess that defies the point of an opinionated git extension. I just thing this opinion may be dismissed too quickly. |
@bastienboutonnet if you name it as |
I was not aware you were sticking to those rules. Just so that I can understand. What point does it break actually? I'm trying to see how the default merge commit message from github does not violate those conventions. @fregante what was the old feature like:
Because that could be good also :) |
This comment has been minimized.
This comment has been minimized.
I moved the “dimmed merge commits” suggestion to #2827 As a solution to this issue, a new feature could be added: |
@fregante I totally buy that! |
Nice idea but I suggest one thing to consider: It seems visually easier to skip a merge commit if it has almost exactly the same title as the normal commit. For example, this:
seems easier to skim than this:
|
It's easier to skim it if you just avoid merge commits altogether, what's the point? Change the politics if it doesn't help your work. Squash commits and the problem disappears. #2827 will help reduce the noise at least on GitHub.com |
@fregante fair enough, agreed |
I opened a more specific issue ⬆️ |
Just to add my perspective, we use both merge commits and "squash and merge" in our project, using merge commits where it's necessary or desirable to preserve history, like for a feature branch. I like linear history for seeing what's actually happened on the default branch and even if you use merge commits you can get this with Digging a bit more into the details, in our project we actually have two independent long-lived branches which we merge back and forth between. Doing that without merge commits would be infeasible (I experimented with it). |
Thanks, this should be the official workaround for those who want this feature in default merge commits :-) |
My merge commits are no longer renamed automatically to sync with the PR title. Only squash commits are being renamed.
Perhaps can this functionality be restored as a separate feature, to rename merge commits, not only the squash commits?
This was always there, but I believe it was removed via #2738.
The text was updated successfully, but these errors were encountered: