search

camunda-community-hub / community-action-maven-release

Opinionated GitHub action to release community projects to Maven Central
Apache License 2.0
7 stars 4 forks source link

Configure git branch #37

Closed remcowesterhoud closed 2 years ago

remcowesterhoud commented 2 years ago

This enables users to add a branch as input to this action. When passed this branch will be used when updating the versions in maven. By default this branch will be the default branch of the repository (similar to the old behaviour).

This change gives users more freedom over their release process. For instance, if I want to support multiple versions and have different branches for managing this.

Imagine the following branches:

  1. main
  2. stable/1.0
  3. stable/1.1

When I want to do a patch release on version 1.0, I want the versions to be updated on the stable/1.0 branch. I'd set the branch input to stable/1.0 to achieve this. Without this change making a new patch release for version 1.0 will result in an update of the main branch. Where the versions would've been 1.1 before, they'd be updated to 1.0 because of this patch.

celanthe commented 2 years ago

Thank you so much for this wonderful contribution! LGTM! I'll let another team member know about this issue and once we have another approval, we can get this merged!

Thank you again. This is great!