forked from issue-ops/semver
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CONTRIBUTING
47 lines (35 loc) · 1.35 KB
/
CONTRIBUTING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
# Contributing
All contributions are welcome and greatly appreciated!
## Steps to Contribute
> [!WARNING]
>
> Check the `engine` property in [`package.json`](./package.json) to see what
> version of Node.js is required for local development. This can be different
> from the version of Node.js used on the GitHub Actions runners. Tools like
> [nodenv](https://github.com/nodenv/nodenv) can be used to manage your Node.js
> version automatically.
1. Fork this repository
1. Commit your changes
1. Test your changes
1. Make sure to run `npm run all` before committing your final changes!
1. Open a pull request back to this repository
1. Notify the maintainers of this repository for peer review and approval
1. Merge :tada:
The maintainers of this repository will create a new release with your changes
so that everyone can use the new release and enjoy the awesome features of
branch deployments!
## Testing
This project requires **100%** test coverage.
> [!IMPORTANT]
>
> It is critical that we have 100% test coverage to ensure that we are not
> introducing any regressions. All changes will be throughly tested by
> maintainers of this repository before a new release is created.
### Running the Test Suite
Simply run the following command to execute the entire test suite:
```bash
npm run test
```
> [!NOTE]
>
> This requires that you have already run `npm install`