зеркало из https://github.com/electron/trop.git
37 строки
1.7 KiB
Markdown
37 строки
1.7 KiB
Markdown
## Contributing
|
|
|
|
[fork]: /fork
|
|
[pr]: /compare
|
|
[style]: https://standardjs.com/
|
|
|
|
Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
|
|
|
|
This project adheres to the Contributor Covenant
|
|
[code of conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md).
|
|
By participating, you are expected to uphold this code.
|
|
|
|
## Submitting a pull request
|
|
|
|
1. [Fork][fork] and clone the repository
|
|
1. Configure and install the dependencies: `npm install`
|
|
1. Make sure the tests pass on your machine: `npm test`, note: these tests also apply the linter, so no need to lint seperately
|
|
1. Create a new branch: `git checkout -b my-branch-name`
|
|
1. Make your change, add tests, and make sure the tests still pass
|
|
1. Push to your fork and [submit a pull request][pr]
|
|
1. Pat your self on the back and wait for your pull request to be reviewed and merged.
|
|
|
|
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
|
|
|
|
- Follow the [style guide][style] which is using standard. Any linting errors should be shown when running `npm test`
|
|
- Write and update tests.
|
|
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
|
|
- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
|
|
|
|
Work in Progress pull request are also welcome to get feedback early on, or if there is something blocked you.
|
|
|
|
## Resources
|
|
|
|
- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
|
|
- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
|
|
- [GitHub Help](https://help.github.com)
|