feat: setup ci with github actions #5
Closed
Conversation
This file contains 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
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.
Overview
Closes #3
I created a ci to run on all pull requests to prevent problems with tests, linting, and build.
I did not make automatic publish on release yet because I don't found a good solution to did it with release-it. We have a lot of ways to try to automate publishing, and I need your help to pick the best solution for this project.
Suggestion: we can remove release-it and make a workflow with
semantic-releaselike I did on this commit for react-native-mask-text library.semantic-release can make automatic release and publish when you merge to main (or to a release branch) and it automatically resolves semantic versions according to your commit merge messages.
Todo