feat: update build and release\ #8
Merged
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.
Description
This is a
Checklists
Commit style
Changes are on a branch with a descriptive name eg.
fix/missing-queue,docs/setup-guideCommits start with one of
feat:fix:docs:chore:or similarNo excessive commits, eg: there should be no
fix:commits for bugs that existed only on the PR branch (see guide-to-interactive-rebasing)Protected files
The following files should not change unless they are directly a part of your change.
yarn.lock(unless package.json is also modified, then only the new/updated package should be changed here)package.json(renovate bot should handle all routine updates)tsconfig.json(only make it stricter, making it more lenient requires more discussion)