-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
misc: Update and fix contribution guide (#70)
* misc: Update and fix contribution guide * Update CONTRIBUTING.md Co-authored-by: Romain Sempé <[email protected]> --------- Co-authored-by: Romain Sempé <[email protected]>
- Loading branch information
1 parent
cf52f68
commit 1adfed5
Showing
2 changed files
with
53 additions
and
24 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
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,28 @@ | ||
## Pull Request template | ||
|
||
Please, go through these steps before you submit a PR. | ||
|
||
1. Make sure that your PR is not a duplicate. | ||
2. If not, then make sure that: | ||
|
||
a. You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the `fix/` or `feature/` prefixes. Good examples are: `fix/signin-issue` or `feature/issue-templates`. | ||
|
||
b. You have a descriptive commit message with a short title (first line). | ||
|
||
c. You have only one commit (if not, squash them into one commit). | ||
|
||
d. `python3 -m pytest tests` doesn't throw any error. If it does, fix them first and amend your commit (`git commit --amend`). | ||
|
||
3. **After** these steps, you're ready to open a pull request. | ||
|
||
a. Give a descriptive title to your PR. | ||
|
||
b. Describe your changes. | ||
|
||
c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). | ||
|
||
d. Add the corresponding labels to your pull request (ex: feature, improvement, bug...) | ||
|
||
IMPORTANT: Please review the [CONTRIBUTING.md](../CONTRIBUTING.md) file for detailed contributing guidelines. | ||
|
||
**PLEASE REMOVE THIS TEMPLATE BEFORE SUBMITTING** |