We can make this area more succinct. Let's do that.

MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/142705

Changelog: fixed

Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/22236

**Problem**

Fast-forward MR strategy doesn't create a merge commit. That hides
revert/cherry-pick button on the merge request, because there is no
merge commit related to the merge request.

However, this functionality should be available  when the merge request
was squashed or it had only one commit.

**Solution**

Use `squash_commit` or `merged_commit` as a point for revert/cherry
pick.

Changelog: changed

The info in the previous commit was correct, but not written in
GitLab style. This commit brings the statement up to spec.

MR: gitlab.com/gitlab-org/gitlab/-/merge_requests/142286

extend the merge_request_finder by functions to filter by merge_user
and add frontend and API code to display the additional filters

Changelog: added

Signed-off-by: Martin Schurz <Martin.Schurz@telekom.de>

Blend these into the page so I can edit.

Changelog: removed

- Set feature flag ff_require_saml_auth_to_approve to default enabled
  Flag was set to 100% enabled on gprd on 2023-11-29 21:45 UTC by
  dblessing
  https://gitlab.com/gitlab-org/gitlab/-/issues/431714#note_1722976173

- Refs:
  https://gitlab.com/gitlab-org/gitlab/-/issues/431714

Changelog: changed
EE: true

As part of our updated style, add publication dates to YouTube
videos. These are the only videos for Code Review.

Simplify the opening section somewhat. Remove mentions of GitLab 13.
Add a sentence that explains MRs can't be approved after merge.

These crosslinks were updated incorrectly in the most recent docs
update. Let's repair the links so the info is findable again.

This commit updates the Merge-Request
changes docs it adds a section about the new
inline findings feature.

Process the remaining few subheadings for "create a merge request"
for accuracy.

Don't reference the pinned versions of "Merge requests" or "Issues"
even though it's visible. Use the long version.

- Previously, each policy was checking the following things:
  - ai_global_switch ops FF enabled
  - AI license available
  - AI feature available via StageCheck
  - Is the user actually a member of the parent resource? (only members
  can use AI features)
- Now, any permissions checks related to AI features can call
  `Llm::FeatureAuthorizer` and be confident that they are making all of
  the correct checks.
- Follow-up to https://gitlab.com/gitlab-org/gitlab/-/merge_requests/137362

I'm not the entire way through the page, but I'm losing steam and
we can get value from the updates I've done so far. This commit steps
through the first few subheadings on this page, checking each step
of each process, and updating them to match current expectations.

We don't need this image any more.

I can't convince others to add a test, so I should fix these
instances of the word 'may.' It never registers on me as an
issue.

Update the links in all user and admin pages

Because the page felt cluttered to me
Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/425355

This is not used on the current docs website
and needs to be removed for future compatibility
with Hugo.

Changelog: added

Update the beginning of these instructions to match our style
guide.

Because these concepts were duplicates
I put them in a get started page instead
And redirected the Concepts page.

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/425355