nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Update merge commit message

unknown

When you merge pull request, bitbucket by default generate Merge commit message.

User can edit this message in "Merge pull request" dialog.

We are looking for possibility to have another merge commit message by default. Ideally, we want to take Pull request title and put it as merge commit message.

Is it possible to do via bitbucket plugin sdk?

Accepted answers

All comments

Maciej Adamczak

Hi @[deleted]you can't configure a custom default message of the merge commit. What you can do instead, is to edit the commit message before merging the pull request.

What you can do is to watch and vote on this issue:
https://jira.atlassian.com/browse/BSERV-10184

When you add yourself to the watchers, you will get a notification when the feature is implemented.

Thanks,
Maciej

unknown

Thanks for the response. I already gave my vote.

But I also wanted to understand whether it's possible to handle via MergeChecks extension or some other way using SDK?

Maciej Adamczak

I think you should be able to create a custom merge check. Here is the link to the documentation on how to do it:
https://developer.atlassian.com/server/bitbucket/tutorials-and-examples/controlling-when-pull-requests-can-be-merged

The PullRequestMergeHookRequest.getMessage() should return the merge commit message you could validate.

Thanks,
Maciej

unknown

@Maciej Adamczak is there any way to update the message?

John Bain

I would like to be able to generate a template for only merge commits. The "Yet Another Commit Checker" only allows all commit messages to adhere to a specific regex expression, unless you've selected the merge commit to be excluded, specifically. I need only the merge commit to be included, and everything else excluded. Previous versions of BitBucket had a very simple, and easy to parse, via our own automation (--oneline), merge commit message which included the Pull Request, branch, and destination. Super simple. We do not want multiline, as it's too verbose, which doesn't bring any actual meaning to a merge commit, and makes any custom parsing more difficult. What happened to wonderful simplicity of this. Really, even if we could template only our merge commits, this would solve all of our problems. Is there any effort to implement something like that?

Axelsson Torbjörn _Consultant_

It should not change anything about the commit that is "merged" when you do an ff-only "merge". This is avery annoying bug that keeps popping up and interrupting the work flow.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

bitbucket

bitbucket-server

atlassian-sdk

merge

bitbucket-development