Feature Request: Add Support for Multiple Branches in Versioning

[grasmarcussanti129]

Overview

As the project currently stands, the Terraform Module Releaser automates versioning based on commit messages within a single branch. However, many teams work with multiple branches (e.g., develop, staging, production) and would benefit from the ability to version modules in these branches separately.

Suggested Feature

• Enable Versioning Across Multiple Branches: It would be great to have a feature that allows users to specify a branch context for versioning. This would help in managing versions that differ based on the branch environments while still benefiting from the automation features of the module releaser.

Benefits

• Teams can maintain separate, independent version histories based on the branch they are working on.
• Reduces confusion when it comes to managing releases in different environments (e.g., testing versus production).
• Allows for easier rollout of new features and rollback procedures based on specific branch activities.

Implementation Ideas

1. Add a configuration option to specify the branches that should be monitored for versioning.
2. Update the logic for major/minor/patch version increments to consider the specified branches.
3. Ensure documentation is updated to guide users on how to leverage this functionality.

I believe this enhancement would significantly improve the usability of the Terraform Module Releaser, especially for teams operating in complex development workflows.