Updates capitalization of 'push rule'

What does this MR do?

As part of the UX Paper Cuts work in #457239 (closed), clean up some remaining mis-capitalized instances of the string push rules, which should either be all lower-case, or sentence case. Not title case.

Related issues

Related to ✂️ UX Paper Cuts 17.2 → Admin (#457239 - closed)

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product availability details under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

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.

changed milestone to %17.2

added Technical Writing UX Paper Cuts devopsmanage docs-only docsimprovement documentation groupux paper cuts maintenancerefactor sectioncore platform tw-weight5 typemaintenance labels

assigned to @aqualls

added pipelinetier-1 label

mentioned in issue #457239 (closed)

added backend frontend labels

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/api/groups.md (Link to current live version)
• doc/user/group/import/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

Reviewer roulette

Category	Reviewer	Maintainer
backend	@ssuman3 (UTC+5.5, 12.5 hours ahead of author)	@.luke (UTC+12, 19 hours ahead of author)
frontend	@thomasrandolph (UTC+0, 7 hours ahead of author)	@ekigbo (UTC+10, 17 hours ahead of author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

removed docs-only label

changed the description

I think this can go straight to @jivanvl and @hmehra - these changes are small.

requested review from @jivanvl

requested review from @hmehra

approved this merge request

added pipeline:mr-approved label

added pipelinetier-3 label and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.

Before you resolve this discussion, please check the following:

• You are the last maintainer of this merge request
• The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
• This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please resolve this discussion and the set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for a0acd672

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Verify      | 43     | 0      | 4       | 0     | 47    | ✅     |
| Govern      | 69     | 0      | 0       | 0     | 69    | ✅     |
| Data Stores | 31     | 0      | 0       | 0     | 31    | ✅     |
| Create      | 128    | 0      | 12      | 0     | 140   | ✅     |
| Plan        | 67     | 0      | 2       | 0     | 69    | ✅     |
| Package     | 19     | 0      | 12      | 0     | 31    | ✅     |
| Monitor     | 8      | 0      | 0       | 0     | 8     | ✅     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
| Release     | 5      | 0      | 0       | 0     | 5     | ✅     |
| Manage      | 0      | 0      | 1       | 0     | 1     | ➖     |
| Fulfillment | 1      | 0      | 0       | 0     | 1     | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 373    | 0      | 31      | 0     | 404   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

e2e-package-and-test: test report for a0acd672

expand test summary

+-------------------------------------------------------------+
|                       suites summary                        |
+--------+--------+--------+---------+-------+-------+--------+
|        | passed | failed | skipped | flaky | total | result |
+--------+--------+--------+---------+-------+-------+--------+
| Manage | 30     | 0      | 15      | 2     | 45    | ✅     |
| Create | 274    | 0      | 34      | 40    | 308   | ✅     |
| Plan   | 4      | 0      | 0       | 0     | 4     | ✅     |
| Govern | 2      | 0      | 0       | 0     | 2     | ✅     |
+--------+--------+--------+---------+-------+-------+--------+
| Total  | 310    | 0      | 49      | 42    | 359   | ✅     |
+--------+--------+--------+---------+-------+-------+--------+

changed milestone to %17.3

added missed:17.2 label

resolved all threads

mentioned in issue jivanvl/manager-of-one#16 (closed)

enabled automatic add to merge train when checks pass

added this merge request to the merge train at position 2

merged

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label