Represent the GitHub Copilot app modernization agent in migration content#37308
Open
wadepickett with Copilot wants to merge 3 commits into
Open
Represent the GitHub Copilot app modernization agent in migration content#37308wadepickett with Copilot wants to merge 3 commits into
wadepickett with Copilot wants to merge 3 commits into
Conversation
Contributor
|
Fixes #37237 |
Copilot
AI
changed the title
[WIP] Verify Modernization Agent is represented in migration content
Represent the GitHub Copilot app modernization agent in migration content
Jul 3, 2026
Contributor
|
@twsouthwick, Tip Regardless of the path you choose, the GitHub Copilot app modernization agent can assess your solution, generate an upgrade plan, and automate many of the migration steps. For more information, see xref:migration/fx-to-core/tooling. Is this also the right tip for extreme migratons, such as Web Forms → latest Blazor? The rest was just an update to the two articles to bring them inline with the style guide. |
wadepickett
approved these changes
Jul 3, 2026
wadepickett
left a comment
wadepickett
left a comment
Contributor
There was a problem hiding this comment.
Reviewed, updated, approved.
wadepickett
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #37237
The following has been generated based on the instruction details and suggestions by WadePickett in the tracking issue:
The migration node covered the GitHub Copilot app modernization agent only in
fx-to-core/tooling.md(andstart.md). The landing page and the fx-to-core overview didn't mention or link to it, leaving the agent hard to discover. This adds cross-links; the agent's conceptual content stays sourced fromdotnet/core/porting/....Changes
aspnetcore/migration/index.md— Replaced the two-line stub body with a cross-link paragraph to GitHub Copilot app modernization and Overview of upgrading .NET apps.aspnetcore/migration/fx-to-core/index.md— Added a[!TIP]in "Start here: Choose your migration path" pointing to the agent and<xref:migration/fx-to-core/tooling>, applicable regardless of the chosen path.ms.dateand addedai-usage: ai-assisted(undertitle) on both edited files.Deferred to the dev team
The issue's "extreme" end-to-end scope question (e.g., Web Forms → latest Blazor) and whether to surface the agent in every version-to-version upgrade article are scope decisions requiring ASP.NET Core dev-team sign-off and coordination with @adegeo. No assertions were added for those.
Internal previews