https://www.mediawiki.org/wiki/GitLab/Workflows/Making_a_merge_request covers the technical details of using GitlLab to produce a merge request. That documentation however feels like it could be improved by separating the workflows of creating an MR against a repo where the change author has push privileges (is a project owner/maintainer) vs the more likely workflow of forking the repo to gain push rights. Leaving more technically complex topics like making a working copy dual homed to a read-only remote and a read-write remote for advanced tutorials or footnotes would also be reasonable.
We have folks in the technical community who are well versed in one or the other, but not both, of these MR workflow variations. Providing documentation that clearly shows when to use which workflow and the differences between them should make it easier to provide front line tech support.
