Closed luabida closed 2 years ago
just for the record, the title prefix for this PR would be "ci" or "chore(ci)", but as we also need to cut a new release and we don't have any commit with fix, feat, or breaking change prefix, we are using this PR to trigger the release.
:tada: This PR is included in version 1.2.1 :tada:
The release is available on:
1.2.1
Your semantic-release bot :package::rocket:
Description
Added a step that will return 0 if the grep finds the semantic-release tag in the PR title.
Related Issue
Fix #183
Checklist
CODE_OF_CONDUCT.md
document.CONTRIBUTING.md
guide.chore(docs):
for Examples / docs / tutorials / dependencies updatefix:
for a bug fix (non-breaking change which fixes an issue).chore(improvement):
for an improvement (non-breaking change which improves an existing feature).feat:
for a new feature (non-breaking change which adds functionality).breaking change:
for a breaking change (fix or feature that would cause existing functionality to change).chore(security):
for a security fix.Note: The title prefix can be also expanded with more information inside the parenthesis. Some examples for a full title (prefix + message):
fix(login): Fix the login page
.feat(forecast): Add a weather forecast page
.chore(security-login): Add a weather forecast page
.