[WIP] Add auto-release support #351
Conversation
Modelled after what @manageiq/react-ui-components does: ManageIQ/react-ui-components#38 + ManageIQ/react-ui-components#84 Fixes #189
|
TODO: set |
|
Checked commit https://github.com/himdel/ui-components/commit/74bc208bc1782b6ef8804c6d29dc7c67a3993552 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 **
|
|
This pull request is not mergeable. Please rebase and repush. |
|
WIP, update and rebase first, |
|
This pull request has been automatically closed because it has not been updated for at least 6 months. Feel free to reopen this pull request if these changes are still valid. Thank you for all your contributions! |
|
This pull request is not mergeable. Please rebase and repush. |
|
Closing, no autorelease here, we will be moving things to react-ui-components. |
Add semantic-release, enables npm autorelease on master merges.
Modelled after what ManageIQ/react-ui-components does:
ManageIQ/react-ui-components#38 - description and config
ManageIQ/react-ui-components#84 - autotooling
Fixes #189
This will not affect merges on gaprindashvili or hammer branches, only master.
This will not do anything with bower, only a npm package.
If you don't do anything special, merged PR will mean a patch release.
If you add
<no>(case insensitive) to the commit message, no release will happen.Otherwise, you can use
<x.?.?>to release a major version,<?.x.?>for a minor one, and<?.?.x>for a patch release (the default).