-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(contribution): create contribution guideline (CONTRIBUTING.md)
- Loading branch information
Showing
1 changed file
with
14 additions
and
0 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
# Contribution guideline | ||
|
||
## Create a GitHub Pull Request | ||
|
||
### 1. Fork the repository | ||
### 2. Make changes, commit them to your fork | ||
- As the release process is automated, write your commit message according to the [semantic-release documentation](https://github.com/semantic-release/semantic-release?tab=readme-ov-file#commit-message-format)'s default config | ||
### 3. Push your changes to your fork | ||
### 4. Create a pull request | ||
- Go to https://github.com/emartech/escher-suiteapi-js/compare | ||
- Select your fork and branch as head | ||
- Select emartech/escher-suiteapi-js and master as base | ||
### 5. The code has to be approved and merged by a maintainer | ||
- Ask the @js-maintainers user group on Slack for review |