chore: setup release please to support changelog development#443
Open
lwasser wants to merge 2 commits intoall-contributors:mainfrom
Open
chore: setup release please to support changelog development#443lwasser wants to merge 2 commits intoall-contributors:mainfrom
lwasser wants to merge 2 commits intoall-contributors:mainfrom
Conversation
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
1 participant
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.
THis PR closes #442
It creates a config file for release please. i tested this on my fork and it seems to work well!
It uses conventional commits to trigger releases so if we create a new pr with a commit that has fix, or feat etc it will trigger a build. this then pushes us one step closer to creating an actual npm release.
Why:
How:
Checklist: