BitBucket merge-squash flooded with intermediate messages

Taw Moto July 22, 2020

My scenario is this:

I have a `feature/x` branch where I commited 20-30 times, then I want to `merge squash` on master.

I am doing this using the BitBucket web interface, but it seems that all 20-30 commit messages are preserved, which is bad.  I don't really need all the intermediate commit messages, just the main commit message that I write in the "merge" dialog..

We should have the possibility to "keep/remove intermediate messages" or smth, via a checkbox.

When `git merge squash` in cmdline, this does not happen, it happens only in Bitbucket.

Is there a workaround for this?

Thanks.

 

 

 

1 comment

Eli Black March 10, 2022

It looks like you can set "commit summaries" to 0. This should pop up a a window that asks you to provide a custom commit message 🙂

See https://jira.atlassian.com/browse/BSERV-8384?focusedCommentId=2485047&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2485047 and the "Commit summaries" section of https://confluence.atlassian.com/bitbucketserver076/pull-request-merge-strategies-1026535042.html

I haven't had a chance to try this yet myself, but it looks hopeful! 🙂

简涛 January 31, 2023

No where to change commit summaries

Eli Black February 2, 2023

@简涛 It's working for us 🙂  After clicking "Merge", there are two text fields, under the label "Commit message", that can be edited.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events