We use github-tag-action to generate semver versions and then release notes for a number of projects. We are also using it in a monorepo with 2 different apps and this is where we're running into issues. Because github_tag_action looks at all the commits since the last tag we end up with a bunch of unrelated changes being considered e.g.
feat: Update frontend
feat: Add new python library
Where ideally we'd only have one bump per app.
Solution
This is quick illustrative PR to explain how I might use the github-tag-action with a mono repo. In this change I added a path based filter to the getCommits - it's not wired through to the config / params that mean people can use it but I wanted to share this approach early to get some feedback before going any further.
Problem
We use
github-tag-actionto generate semver versions and then release notes for a number of projects. We are also using it in a monorepo with 2 different apps and this is where we're running into issues. Becausegithub_tag_actionlooks at all the commits since the last tag we end up with a bunch of unrelated changes being considered e.g.Where ideally we'd only have one bump per app.
Solution
This is quick illustrative PR to explain how I might use the
github-tag-actionwith a mono repo. In this change I added a path based filter to thegetCommits- it's not wired through to the config / params that mean people can use it but I wanted to share this approach early to get some feedback before going any further.Thoughts, comments, criticisms welcome.