feat: allow exclusion of scopes from analyze_commits #16
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.
Discussed over in #7
I thought I'd put out the PR here, because otherwise it'll just get abandoned - it should work as expected - when you call
analyze_commits(ignore_scopes: ['android','windows'])
, it will ignore any commits which have those scopes within them.What I'm not happy about, is that even if the commits are ignored by the
analyze_commits
action, they would still be included in theconventional_changelog
.Ideally, excluding a commit like this would create something like a
Fastlane::Actions::SharedValues::RELEASE_COMMITS
array, which would not include the ignored scopes, and theconventional_changelog
action would automatically read from that array.But that's more of a change to the way this plugin works, so would have to be handled separately 😄
I'm not going to have any time to touch this for the next few months, sadly. So if anybody wants to build upon it, etc, they're more than welcome to.