Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit dd8a6fa

Browse files
aashilamueller
authored andcommitted
dev-7360: Explain the meaning of prefix [MRG + 1] and [MRG + 2] in the title of the pull request. (#7636)
* File updated: doc/developers/contributing.rst
1 parent cbd3bca commit dd8a6fa

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

doc/developers/contributing.rst

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -185,11 +185,13 @@ rules before submitting a pull request:
185185

186186
* Please prefix the title of your pull request with ``[MRG]`` if the
187187
contribution is complete and should be subjected to a detailed review.
188-
Incomplete contributions should be prefixed ``[WIP]`` to indicate a work
189-
in progress (and changed to ``[MRG]`` when it matures). WIPs may be useful
190-
to: indicate you are working on something to avoid duplicated work,
191-
request broad review of functionality or API, or seek collaborators.
192-
WIPs often benefit from the inclusion of a
188+
Two core developers will review your code and change the prefix of the pull
189+
request to ``[MRG + 1]`` and ``[MRG + 2]`` on approval, making it eligible
190+
for merging. Incomplete contributions should be prefixed ``[WIP]`` to
191+
indicate a work in progress (and changed to ``[MRG]`` when it matures).
192+
WIPs may be useful to: indicate you are working on something to avoid
193+
duplicated work, request broad review of functionality or API, or seek
194+
collaborators. WIPs often benefit from the inclusion of a
193195
`task list
194196
<https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-comments>`_
195197
in the PR description.

0 commit comments

Comments
 (0)