Update title for managing access migration from Azure DevOps

[jessehouwing]

Why:

Closes: #45144

What's being changed (if available, include any code snippets, screenshots, or gifs):

The title for managing access during migrations from Azure DevOps has been updated to "Managing access for a migration from Azure DevOps" to align with the terminology used for GitHub Enterprise Server (GHES) and Bitbucket Server (BBS) migrations.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
migrations/ado/manage-access.md	fpt ghec	fpt ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Copilot]

Pull request overview

Updates the Azure DevOps migration access article title so AUTOTITLE links identify the applicable source platform.

Changes:

• Renames the article to “Managing access for a migration from Azure DevOps.”

[jessehouwing]

Hmmm renaming the slug would be a bit overreaching I think, based on its short title it should have been 2-manage-access.

How to proceed here?

• Remove the [AUTOTITLE] in the troubleshooting section?
• Rename this doc to 2-manage-access.md and add redirects?
• Rename this doc to managing-access-for-a-migration-from-azure-devops.md and add redirects (in line with BBS and GHES)?

[Sharra-writes]

@jessehouwing Unfortunately this isn't as simple as updating the title, because the title affects the URL. I'm not sure why the short title has the 2 in front of it, though, and if that could be removed, the URL would match the short title, and that would satisfy the check. Let me find out.

[Sharra-writes]

@jessehouwing These are the instructions I've been given for updating the title:

They'd run this in their codespace or docs-internal checkout:

npm run move-content -- --no-git content/migrations/ado/manage-access.md content/migrations/ado/manage-access-for-a-migration-from-azure-devops.md

This script should take care of all the things, like the rename and setting redirects. I'm not 100% sure it updates journey landing pages though.

So they should make sure the path in the journey landing page index.md file says /manage-access-for-a-migration-from-azure-devops vs /manage-access:

https://github.com/jessehouwing/docs/blob/f19a0135b2fe88a1ca17efbadb1d2bf14eb332b4/content/migrations/ado/index.md?plain=1#L10

Hopefully that all makes sense. If you have questions, I will ping in the person who is helping me out with this, since I've never done it before.