Skip to content

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

I obviously require more pedantic instructions than some people. Hopefully this minor change to the workflow documentation will help other people who face the same issue.

The issue being addressed is updating a Merge Request (MR). It was not at all clear to me that simply by using git push --force origin topic/branch that the current MR would somehow magically be resubmitted with the updated code. I looked around within the MR on Github trying to find some kind of force(push) button on ay webpage associated with the MR.

I still don't really understand how this works - how does the MR get updated with a new commit hash ? - but, at least I can realize that it happens with my ammended description.

Topic-rename: doc-review

Edited by Brad King

Merge request reports