Open
Conversation
This WON'T work until [it's installed](https://github.com/apps/rollingversions/installations/new) and the NPM token set (even if the package is deployed on the [GH package registry](https://github.com/features/packages)).
amirhmk
approved these changes
Jun 22, 2020
Collaborator
Author
|
@misterpeddy Do you know if there's a |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What?
As we don't have any automated release pipelines and standard solutions like Semantic Release don't work as we use an unconventional commit convention.
I've come across a tool developed by Forbes Lindsay and according to him it would suit our use case (see his response on a Medium article).
Why?
Automated release process > manual release process.
Note
package registry).