Slack merge strategy does not adhere to bitbucket cloud's merge strategy

Hello

We are using bitbucket cloud for our git repo and also use slack. We are using integration of bitbucket into slack.

We have noticed that the merge through slack does not follow the default strategy which is defined in our project in bitbucket. So every time, we have to manually change the strategy while doing merge from slack. Sometimes people forget and we end up with a situation of our git history looking not like what we want to.

It would be great to have slack merge follow the same strategy as bitbucket or provide a setting to set the strategy in the bitbucket app within slack.

Thanks