simon/semantic-release
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

feat: allow to exclude commits from analysis

Browse Source
This commit is contained in:
Pierre Vanduynslager
2018-01-06 00:11:20 -05:00
parent fd54eead6f
commit 53f3de6786
3 changed files with 56 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/support/FAQ.md
+4
View File
@@ -123,6 +123,10 @@ See [Artifactory - npm Registry](https://www.jfrog.com/confluence/display/RTF/Np
You can trigger a release by pushing to your Git repository. You deliberately cannot trigger a *specific* version release, because this is the whole point of semantic-release.
### Can I exclude commits from the analysis?
Yes, every commits that contains `[skip release]` or `[release skip]` in their message will be excluded from the commit analysis and won't participate in the release type determination.
## Is it *really* a good idea to release on every push?
It is indeed a great idea because it *forces* you to follow best practices. If you don’t feel comfortable releasing every feature or fix on your `master` you might not treat your `master` branch as intended.