diff options
| author | Alejandro Piñeiro <[email protected]> | 2019-05-16 11:32:23 +0200 |
|---|---|---|
| committer | Alejandro Piñeiro <[email protected]> | 2019-05-16 16:16:32 +0200 |
| commit | 16a1ef7860e4f0ce27faceb6874870d8d6fd5a56 (patch) | |
| tree | 2a32a7b40863f1af810be3af01229f48de25cbec /docs/submittingpatches.html | |
| parent | 4171a26193e0d155f2e825b2f6e7d478932ddcf5 (diff) | |
docs: advice to resolve discussion on gitlab MR doc
For newcomers to gitlab, it is not evident that it is better to press
the "Resolve Discussion" button when you update your branch handling
feedback.
v2:
* Fix several grammar nits, reorder, use new corrected text (Connor
Abbot)
* Use "reviewers", instead of reviewer (Eric Engestrom)
Reviewed-by: Connor Abbott <[email protected]>
Reviewed-by: Eric Engestrom <[email protected]>
Diffstat (limited to 'docs/submittingpatches.html')
| -rw-r--r-- | docs/submittingpatches.html | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index 020e73d09ec..48cc6768b46 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -258,6 +258,9 @@ your email administrator for this.) </p> <ul> <li>Make changes and update your branch based on feedback + <li>After an update, for the feedback you handled, close the + feedback discussion with the "Resolve Discussion" button. This way + the reviewers know which feedback got handled and which didn't. <li>Old, stale MR may be closed, but you can reopen it if you still want to pursue the changes <li>You should periodically check to see if your MR needs to be |