Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Custom properties in releaseFinishMergeMessage is treated as literals #163

Closed
steve-todorov opened this issue Mar 18, 2019 · 5 comments
Closed

Custom properties in releaseFinishMergeMessage is treated as literals #163

steve-todorov opened this issue Mar 18, 2019 · 5 comments
Assignees
@aleksandr-m

Comments

@steve-todorov
Copy link

Issue

According to the docs you can use custom properties in the commit messages. However, once we've configured our releaseFinishMergeMessage to be [release] Merge branch release/@{version} the commit message was actually literal (check here)
@aleksandr-m aleksandr-m self-assigned this Mar 18, 2019
@aleksandr-m
Copy link
Owner

The releaseFinishMergeMessage was added in #135 and currently it is missing @{version} replacement.

@steve-todorov
Copy link
Author

Awesome! Many thanks for fixing this so fast! Do you plan to cut a release soon?

@carlspring carlspring mentioned this issue Mar 23, 2019
Open
61 tasks
@aleksandr-m
Copy link
Owner

@steve-todorov 1.12.0 is out. Enjoy!

@steve-todorov
Copy link
Author

Great! Thanks for letting me know and for all your hard work! :)

@s-berdnikov
Copy link

The same problem still exists with featureSquashMessage (version v1.20.0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aleksandr-m aleksandr-m

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@steve-todorov @aleksandr-m @s-berdnikov