Details
-
Suggestion
-
Resolution: Won't Fix
Description
Hi everyone.
I want to tell you about our bad experience with a sqhash commit option in Pull Request optons.
When you try to make a sqhash commit based on other squashed commits your system could become to an absolutely unstable state.
Once, one of our colleagues has merged the base branch into his develop branch where was lots of sqhashed commits with very big commit messages and when he has merged his PR, his new sqhashed commit message was of million lines of text.
Some time after that we have started to point out that our systems cannot work with such big commit messages.
Bitbucket itself denying to show this commit in its commit history, responding with the 500 response code.
Whan can I ask you guys is to set-up a limit for a sqhashed commit message.
While users are not able to limit sqashed commits messages there is a big bomb hidden instide of this option.
So I request you guys to make a new feature to have an ability to limit squash commit on PR merge.
Thank you.