Update title for managing access migration from Azure DevOps - #45145
Update title for managing access migration from Azure DevOps#45145jessehouwing wants to merge 2 commits into
Conversation
Renamed to be in line with GHES and BBS migrations. Fixes: github#45144
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
Hmmm renaming the slug would be a bit overreaching I think, based on its short title it should have been How to proceed here?
|
|
@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. |
|
@jessehouwing These are the instructions I've been given for updating the title:
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. |
|
Hi @jessehouwing and thanks for raising an issue and PR for this Unfortunately, we can't accept this contribution—the file was already named what you're proposing to rename it to at one point as you'll note here. Whilst it's not impossible to reverse that change from a technical perspective, I have to take the position that the team made the change intentionally. Thanks for your interest in the GitHub docs—sorry this isn't the answer you were hoping for, but we hope to see you in future. |
|
Instead of using auto-title, is it then an option to manually set the title in the linked locations? |
|
Okay
…On Wed, 12 Aug 2026 at 15:25 Jesse Houwing ***@***.***> wrote:
*jessehouwing* left a comment (github/docs#45145)
<#45145 (comment)>
Instead of using auto-title, is it then an option to manually set the
title in the linked locations?
—
Reply to this email directly, view it on GitHub
<#45145?email_source=notifications&email_token=CBJNDRSQR5AL4D7BCCRIO335JQSWXA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRWGQZDINRTGM22M4TFMFZW63VGNVQW45LBNSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5264246335>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CBJNDRQUJE2DP3ZJITJETAL5JQSWXAVCNFSNUABFKJSXA33TNF2G64TZHMYTQOJWGIYTMMBXHNEXG43VMU5TIOBXGQ4TMOBYGMZKC5QC>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
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: