Closed alapierre closed 3 years ago
true, defining the commit name after squash would be a nice feature
Currently, to work around the problem, I turn off the automatic pushing of the commit after merging by:
<pushRemote>false</pushRemote>
next I change the name of the commit manually and push it manually
@alapierre @karolbryzgiel 1.17.0 is out.
greate, thank you!
wt., 7 gru 2021 o 15:12 Aleksandr Mashchenko @.***> napisał(a):
@alapierre https://github.com/alapierre @karolbryzgiel https://github.com/karolbryzgiel 1.17.0 is out.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aleksandr-m/gitflow-maven-plugin/issues/287#issuecomment-987962004, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNVILLJLRVKVP4MBRYEV53UPYI3DANCNFSM4ZIOJWLQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
currently after
commit message is only: feature/feature_name