Update the how-to-get-help handbook page to reflect the move from multiple repositories into a single Repository

Why is this change being made?

This change is being made as an output to the following EPIC : Future proof the RFH process by migrating all the repositories to a single repository

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update file how-to-get-help.md

---

added HandbookContent label

assigned to @jlyttle

Note to be merged until the end of business on Friday the 13th of December 2025

Using combined codequality.json: vale-codequality.json linkcheck.json

Pipeline Failure - Linting Errors

One of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes, you'll find the code quality report above which can link you to where the error is in your code. Additionally, below you'll find a table of the errors. The table has links to the lint rules so you can find more information on how to fix the issue(s).

Rule	File	Line	Error

If you are renaming, moving, or deleting pages, please check the Code Quality report, or the hugolint job's artifact files, to see if there are any related broken links.

If you need more help please reach out on Slack in #mr-buddies.

mentioned in issue gitlab-com/support/support-team-meta#6514 (closed)

added 1 commit

• ef16fb14 - Update how-to-get-help.md

Compare with previous version

Just a couple of suggested changes, John. All else looks right to me. Thank you!

added 1 commit

• 2171f7d4 - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

resolved all threads

added 1 commit

• cf67968c - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

Thanks @mdunninger

marked this merge request as ready

approved this merge request

added 1 commit

• df0b8da9 - Update file ai_features.md

Compare with previous version

reset approvals from @vparsons by pushing to the branch

approved this merge request

added this merge request to the merge train at position 2

merged

mentioned in commit 78252038