-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
6
-
3
-
When creating a Pull Request, the description of it is automatically filled out based off the commits linked to it.
However, long commits are truncated and users have to manually fix that. It would be great not to truncate the commits/.
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-5198] Don't truncate commit message when generating pull request description
+1 This is a significant problem. If any detail about what is being committed is included in the commit message, it's being cut off after one sentence and replaced with `...`
The git history now has no substantial detail about the commits being made.
I agree with Martin (from way back in 2014!).
This shouldn't be a suggestion but rather a bug fix. very weird that we get only part of the commit message and can't get the full text.
This problem has been bothering and annoying our team since we began to use Bitbucket for managing code source and code veview.
We often need to use "git log --merges" to see all the pull request commits. So if the commit message is truncated, we should lost much information.
This problem has been bothering and annoying me for a few weeks now until I even recognised it! It is not really user-friendly if the entire commit message is not analysed for smart commits and also for triggers that I write myself. Especially as I like to attach the content as a comment in the issue to inform the reporter. But if half of the information is cut out, it doesn't make sense.
David Gloe
added a comment - We have a tool that parses pull request messages. When the message gets truncated the tool doesn't function correctly. It's very annoying to have to manually copy the commit message into the pull request every time.
David Gloe
added a comment - We have a tool that parses pull request messages. When the message gets truncated the tool doesn't function correctly. It's very annoying to have to manually copy the commit message into the pull request every time. Martin, I agree. My guess is that switching this to a suggestion was a way to get it out of someone's backlog. This seems like a small enough fix with a big enough impact to justify it being handled promptly.
Martin Apel
added a comment - I'm somewhat astonished to see this converted from a bug report into a suggestion with low priority.
This is something which annoys a couple of users (including our whole development team), should not be hard to fix and has been lurking around for half a year now. For me, this is clearly a bug, not a low-priority suggestion.
Martin Apel
added a comment - I'm somewhat astonished to see this converted from a bug report into a suggestion with low priority.
This is something which annoys a couple of users (including our whole development team), should not be hard to fix and has been lurking around for half a year now. For me, this is clearly a bug, not a low-priority suggestion. 
Paul Wisner
added a comment - For clarity I described an example based on a "model commit message" at https://answers.atlassian.com/questions/10397092/get-stash-to-stop-truncating-the-git-commit-message .
Paul Wisner
added a comment - For clarity I described an example based on a "model commit message" at https://answers.atlassian.com/questions/10397092/get-stash-to-stop-truncating-the-git-commit-message .
This happens for GitHub integration as well. This is extremely annoying if you also have a tendency to add gitmojis into the beginning part of your commit message ALONG with a Jira ID so something like :construction_worker: JIRA-12345 is already 32 of your 50 characters.