[jira] [Commented] (MRELEASE-980) Provide the ability to control commit messages

["Rienk (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRELEASE-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898229#comment-16898229 ] 

Rienk commented on MRELEASE-980:
--------------------------------

So, this is quite an old PR, but this is exactly what I need. 
In my case I need to be able to add [skip ci] to the commit messages, to make sure maven release doesn't trigger another build. However, I do need the pipeline to be triggered on the tag. So having more finegrained control on the commit messages is necessary here. 

Is there a way to migrate this PR to Gitbox? Or create a new Pull request there?

 

 

> Provide the ability to control commit messages
> ----------------------------------------------
>
>                 Key: MRELEASE-980
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-980
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>          Components: prepare
>    Affects Versions: 2.5.3
>            Reporter: Stephen Colebourne
>            Priority: Major
>             Fix For: 3.0.0
>
>
> The commit messages used by maven-release-plugin are rather ugly to my eyes. While the comment prefix provides some control, what is really needed is to be able to change the whole message from xml configuration.
> I've implemented this here: 
> https://github.com/jodastephen/maven-release/commit/35b2a50900cfc8e8fca88a94e46985a09e538e86 (all rights granted to Apache - I'm still a committer at Apache Commons.
> It adds four new properties that allow the commit message to be controlled at various points. The commit message can be configured using `@{}` style inserts. There are more messages that could be controlled, but these were all I needed.
> Note that issue MRELEASE-706 originally requested this feature, but it was closed due to inactivity.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)