Closed erodewald closed 5 years ago
As you can see in the documentation, the plugin use by default the release rules from default-release-rules.js.
Your commit with an Emoji do not match any release rule (there is no rule for :sparkles:
).
Your other commits do not match the Angular convention not the regex you configured.
Your commit subject is supposed to be feat: Remove emoji commit
but instead you put that in the body and the subject is Merge pull request #4 from erodewald/base-features
.
Your commit subject is supposed to be feat: Remove emoji commit but instead you put that in the body and the subject is Merge pull request #4 from erodewald/base-features.
I didn't expect the merge commits to trigger a release, but I did expect the following commit to trigger:
[2:41:56 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: feat: new feature (ci test)
That's a subject-only commit with no emoji prefix.
I'm having trouble convincing my configuration to see release-worthy commits. I have included a snippet from numerous attempts I've tried:
At some point in the above, I abandoned
emoji
prefixes because I thought it might be messing up the analyzer. No dice.package.json
:config/release.config.js
:I'm sure I have misconfigured it, but I'm just not seeing what's tripping up the commit analyzer. Help would be great :)