Skip to content

Update default-branch instructions for style standards

Amy Qualls requested to merge 378499-aqualls-set-branch-names into master

What does this MR do?

The changes in Write documentation for default branch names fr... (#378499 - closed) introduced a navigation change for the Default branch feature documented in https://docs.gitlab.com/ee/user/project/repository/branches/default.html. Because the page had some outdated language as well, it made sense to do the cleanup of the language in this MR, and do the docs work for the new feature separately.

Related issues

Related to Write documentation for default branch names fr... (#378499 - closed) and cleans up existing language so I don't try to do it as part of documenting the feature itself.

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 you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

  • 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.

Merge request reports