Details
-
Suggestion
-
Resolution: Done
Description
Currently when you merge a pull request through the Stash web front-end, you do not have full control of the commit message. This leads to polluted commit logs on master.
In particular, my group would like to use the squash merge strategy and have clean commit messages once the pull request is accepted. The only way to work around this issue that I am aware of is outlined here:
https://answers.atlassian.com/questions/283338/pull-requests-squashed-commits-remote-merges?continue=https%3A%2F%2Fanswers.atlassian.com%2Fquestions%2F283338%2Fpull-requests-squashed-commits-remote-merges&application=acac
This behavior means that what should be a 1 click operation is turned into a more laborious and error prone process.
Attachments
Issue Links
- causes
-
BSERV-10744 Custom commit message not applied when 'merge dialog' is submitted
-
- Closed
-
-
PS-79248 Loading...
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
- relates to
-
- Closed
- was split into
-
- Closed
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-