Skip to content

Commit 9e7c9b3

Browse files
committed
Moar changes yet againz!
1 parent f42e7f9 commit 9e7c9b3

File tree

3 files changed

+26
-162
lines changed

3 files changed

+26
-162
lines changed

docs/core/porting/github-copilot-app-modernization-example.md

Lines changed: 0 additions & 151 deletions
This file was deleted.

docs/core/porting/github-copilot-app-modernization-overview.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,26 @@ The following upgrade paths are supported:
7272
- Modernize your code base with new features.
7373
- Migrate components and services to Azure.
7474

75+
## How does it work
76+
77+
Once you request the Modernization agent to upgrade or migrate your app, Copilot analyzes your projects and their dependencies, and then asks you a series of questions about the upgrade or migration. After you answer these questions, a plan is written in the form of a Markdown file. If you tell Copilot to proceed with the upgrade or migration, it follows the steps described in the plan.
78+
79+
You can adjust the plan by editing the Markdown file to change the upgrade steps or add more context.
80+
81+
### Perform the upgrade or migration
82+
83+
Once an plan is ready, tell Copilot to start using it. Once the process starts, Copilot lets you know what it's doing in the chat window and it opens the **Upgrade Progress Details** document, which lists the status of every step.
84+
85+
If it runs into a problem, Copilot tries to identify the cause of a problem and apply a fix. If Copilot can't seem to correct the problem, it asks for your help. When you intervene, Copilot learns from the changes you make and tries to automatically apply them for you, if the problem is encountered again.
86+
87+
Each major step in the plan is committed to the local Git repository.
88+
89+
### Upgrade and migration results
90+
91+
When the process completes, a report is generated that describes every step taken by Copilot. The tool creates a Git commit for every portion of the process, so you can easily roll back the changes or get detailed information about what changed. The report contains the Git commit hashes.
92+
93+
The report also provides a _Next steps_ section that describes the steps you should take after the upgrade finishes.
94+
7595
## Telemetry
7696

7797
The tool only collects data about project types, intent to upgrade, and upgrade duration. The data is collected and aggregated through Visual Studio itself and doesn't contain any user-identifiable information. For more information about Microsoft's privacy policy, see [Visual Studio Customer Experience Improvement Program](/visualstudio/ide/visual-studio-experience-improvement-program?view=vs-2022&preserve-view=true).

docs/navigate/migration-guide/toc.yml

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -8,17 +8,12 @@ items:
88
- name: Overview
99
href: ../../core/porting/index.md
1010
displayName: copilot, upgrade
11-
- name: GitHub Copilot app modernization
12-
expanded: true
13-
items:
14-
- name: Overview
15-
href: ../../core/porting/github-copilot-app-modernization-overview.md
16-
displayName: copilot, upgrade, faq
17-
- name: Example
18-
href: ../../core/porting/github-copilot-app-modernization-example.md
19-
- name: FAQ
20-
href: ../../core/porting/github-copilot-app-modernization-faq.yml
21-
displayName: copilot, upgrade, faq
11+
- name: GitHub Copilot app modernization Overview
12+
href: ../../core/porting/github-copilot-app-modernization-overview.md
13+
displayName: copilot, upgrade, faq
14+
- name: GitHub Copilot app modernization FAQ
15+
href: ../../core/porting/github-copilot-app-modernization-faq.yml
16+
displayName: copilot, upgrade, faq
2217
- name: Update .NET SDK and Runtime
2318
href: ../../core/porting/github-copilot-app-modernization-faq.yml
2419
- name: Planning your .NET Framework upgrade

0 commit comments

Comments
 (0)