RFC: feat: Adding commit filtering by path #193
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
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. Becausegithub_tag_action
looks 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-action
with 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.