Skip to content

Move branch-retargeting info back to index page

Amy Qualls requested to merge 324957-aqualls-lift-shift into master

What does this MR do?

Move https://docs.gitlab.com/ee/user/project/merge_requests/getting_started.html#branch-retargeting-on-merge out of the "getting started" page and back to the main https://docs.gitlab.com/ee/user/project/merge_requests/ page as part of the slow process of removing the GS page entirely.

MVC because everyone's swamped, and I tried to polish this section instead of just lifting and shifting it. I'm still not in love with how I renamed the subheading. Maybe my reviewer will have more ideas? Please push your changes as part of your review, and tag me afterward to see what you did before I make the next merge request in the series.

Related issues

Related to Revise ./user/project/merge_requests/getting_st... (#324957 - closed) but does not close it.

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Edited by Amy Qualls

Merge request reports