-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
move codeowners from contributing file to the CODEOWNERS file
- Loading branch information
Showing
2 changed files
with
14 additions
and
4 deletions.
There are no files selected for viewing
Validating CODEOWNERS rules …
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,7 @@ | ||
# CODEOWNERS: https://help.github.com/articles/about-codeowners/ | ||
|
||
# Docs | ||
*.md @barriebyron | ||
|
||
# Primary repo maintainers | ||
* @dongsam @kogisin @hallazzang |
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 |
---|---|---|
@@ -1,18 +1,21 @@ | ||
# Contributing | ||
|
||
We welcome contributions from anyone who is willing to create a new PR on farming module, make sure that you read and comply with this document. See the [open issues](https://github.com/tendermint/farming/issues) that we need help with. Feel free to inform us if you are willing to work on any issue. Note that the `master` branch contains the latest development version. | ||
We welcome contributions to our codebase and documentation. | ||
|
||
Before you create a PR on the farming module, make sure that you read and comply with this document. See the [open issues](https://github.com/tendermint/farming/issues) that we need help with. | ||
|
||
Feel free to inform us if you are willing to work on an issue. Note that the `master` branch contains the latest development version. | ||
|
||
We follow standard GitHub best practices: | ||
|
||
- Fork the repository | ||
- Make sure your `branch` is from the tip of `master` branch | ||
- Make some commits to resolve an issue | ||
- Make your commits to resolve an issue | ||
- Submit a pull request to `master` | ||
|
||
General guidance: | ||
|
||
- Make sure you run tests by running `make test-all` locally to see there is any issue | ||
- Review all the checks on your PR and review code coverage report | ||
- Assign reviewers from code owners (@dongsam @kogisin @hallazzang) | ||
- Review all the checks on your PR and review the code coverage report | ||
|
||
Thank you for your contribution! |