Clarify PRs section (#32027)
This commit is contained in:
parent
e6f8428b28
commit
6fea79b67c
|
@ -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
|
help. They should remain focused in scope and avoid containing unrelated
|
||||||
commits.
|
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),
|
implementing features, refactoring code, porting to a different language),
|
||||||
otherwise you risk spending a lot of time working on something that the
|
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
|
Please adhere to the [coding guidelines](#code-guidelines) used throughout the
|
||||||
project (indentation, accurate comments, etc.) and any other requirements
|
project (indentation, accurate comments, etc.) and any other requirements
|
||||||
|
|
Loading…
Reference in New Issue