Skip to content

Update info re: code owners and push rules

Amy Qualls requested to merge 368162-aqualls-fix-notice into master

What does this MR do?

Revises the source files for the deprecation and removal of the push_rules_supersede_code_owners flag, and the generated output:

  • data/deprecations/14-8-remove_ff_push_rules_supersede_code_owners.yml
  • data/removals/15_0/15-0-remove_ff_push_rules_supersede_code_owners.yml
  • doc/update/deprecations.md
  • doc/update/removals.md

@andr3, I'm sending this MR to you because you filed the issue, and you'll be here later this week while I'm out. Because two of the files fall outside the doc/ directory, this merge request will need more review than usual. I believe @marcel.amirault on the TW team has permission to merge this work, so he's likely the easiest person to reroute to for final approval / merge.

Related issues

Closes Improve accuracy and clarity on removal notice for (#368162 - closed)

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