Skip to content
Snippets Groups Projects
Commit d4529b7e authored by Brad King's avatar Brad King Committed by Kitware Robot
Browse files

Merge topic 'doc-review'


b82052fe Help/dev/review: Clarify instructions to update existing merge requests

Acked-by: default avatarKitware Robot <kwrobot@kitware.com>
Merge-request: !6073
parents 09f2f5df b82052fe
No related branches found
No related tags found
No related merge requests found
......@@ -20,8 +20,10 @@ creating a *merge request* ("MR"). The new MR will appear on the
process is managed by the merge request page for the change.
During the review process, the MR submitter should address review comments
or test failures by updating the MR with a (force-)push of the topic
branch. The update initiates a new round of review.
or test failures by updating their local topic branch to fix their commits
(e.g. via ``git commit --amend`` or ``git rebase -i``), and then issuing a
(force-)push of the topic branch to their remote (e.g. ``git push --force``).
This will automatically initiate a new round of review on the existing MR.
We recommend that users enable the "Remove source branch when merge
request is accepted" option when creating the MR or by editing it.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment