diff options
| author | XhmikosR <xhmikosr@gmail.com> | 2020-11-01 08:42:19 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-11-01 08:42:19 +0300 |
| commit | 6fea79b67cd059177d990ebf2cce4e488435ac76 (patch) | |
| tree | ed35a826248c30390676b3ecaf82e68d2863c794 /.github/CONTRIBUTING.md | |
| parent | e6f8428b2850418474649006641c7fc4c0326eff (diff) | |
Clarify PRs section (#32027)
Diffstat (limited to '.github/CONTRIBUTING.md')
| -rw-r--r-- | .github/CONTRIBUTING.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 0055f22078..0913b5b5be 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -123,10 +123,12 @@ Good pull requests—patches, improvements, new features—are a fantastic help. They should remain focused in scope and avoid containing unrelated commits. -**Please ask first** before embarking on any significant pull request (e.g. +**Please ask first** before embarking on any **significant** pull request (e.g. implementing features, refactoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the -project's developers might not want to merge into the project. +project's developers might not want to merge into the project. For trivial +things, or things that don't require a lot of your time, you can go ahead and +make a PR. Please adhere to the [coding guidelines](#code-guidelines) used throughout the project (indentation, accurate comments, etc.) and any other requirements |