How to tell BitBucket Cloud not to shorten commit messages in Slack? Edited

Until now we've been using webhooks to get commit notifications in Slack. They work fine but I wanted to try the BitBucket Cloud application, due to simpler setup and advanced features. However, it shortens messages, how do I turn that off?




4 answers

Hi @Remco Douma@Janne Husberg & @Mathieu Cruts,

I'm the lead for the Bitbucket Cloud for Slack project — thanks for your feedback!

We currently limit the commit message length to the first 50 characters of the first line of the commit. This was based on the 50/72 rule used for commit messages in large open source projects like the Linux kernel and the Git project itself, and also to minimize the chance of messages wrapping in the Slack UI.

However we've received a large amount of feedback from teams (like yourselves) that commonly use longer commit messages and would like to see more of the message in Slack. So we've decided to increase this limit to the first 200 characters of the first line of the commit. Does that sound reasonable?



Hi @Tim Pettersen

Thank you very much for the support! This will be perfect for our needs.


Hi @Tim Pettersen, thanks for coming back on this. Much better than the 50 char limit of course, but personally I'd prefer no clipping at all. I don't care if lines wrap. Alternatively maybe make it an option?

Hi @Remco Douma, thanks for the feedback. We do have to impose a limit of some kind due to platform restrictions, but we'll monitor how often we're truncating and revisit if needed. We can potentially add a config option, but I'm loathe to introduce them unless absolutely necessary due to the UX and implementation complexity they introduce.

Ok @Tim Pettersen, I do understand your hesitation surrounding config options. Like I said; 200 is better than 50. Maybe 1000 is better than 200, I don't know yet ;-)

Ok, I've been playing a while, but for me it doesn't serve its purpose. If I post a commit to Slack I want to see it all, not clipped at some arbitrary length. Compare the two presentations below for the same commit. I hope it's clear the first is preferable. So although I like the look & feel of BitBucket Cloud, I'm going to switch it off and keep using the original solution that doesn't clip.

Good luck with the plugin!


0 votes

Hi Remco! Are you using this integration? If so, it's been created by Slack, so it would be a better idea to contact them and ask if there's a way to show the full commit message when using their integration. 

Hope that helps!


Hi Ana, I'm referring to this integration. According to Slack it's made by you!

So the top one is the one made by Slack and I'm looking at replacing it with yours it seems, but the clipped commit messages are a bit of a dealbreaker for me.

I am experiencing the exact same issue.

At least I'm not alone @Mathieu Cruts! Let's hope @Ana Retamal Ortiz will respond again...

Same here, what's the ETA on an update? 

The integration I used prior to Bitbucket Cloud was one that used Slack webhooks but there were some issues with that (missing notifications) so on advice from Atlassian support I moved to your Bitbucket Cloud integration. 

This issue, of the comment being too short, is a backward step. With the old integration it would display about 380 chars and with a "show more" link. Click that link and you got the entire message along with "show less".

I'd like that functionality please - because it's the "Right thing to do"®

There's obvious use cases - I get notifications on my phone of commits which I can evaluate completely in Slack without clicking through to Bitbucket - very convenient. Also, we have some admin team members who can see our Slack #commit channel but do not have a bitbucket login - this is good!

Also, I'm not aware of an "issue" with messages wrapping in the Slack UI - let them wrap - and please give me the entire commit message - thanks. 

Did you try it recently @robsumo? Because we're not seeing these shortened messages anymore.

Hi @Remco Douma - yes - I only started using the integration yesterday and I'm seeing truncation at 200 chars (is that what you mean by "shortened messages"?). I need to see the entire message.

Ok, for us they generally fit now. I agree I don't see the reason for truncation in the first place.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

657 views 5 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you