From fa839d038c4bb0eba1b0c884e8bf4bd309d0e984 Mon Sep 17 00:00:00 2001 From: ruchira-net <91104117+ruchira-net@users.noreply.github.com> Date: Mon, 30 Mar 2026 15:40:12 +1300 Subject: [PATCH 1/2] Rename tasks.md to progress.md in overview.md --- .../core/porting/github-copilot-app-modernization/overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/core/porting/github-copilot-app-modernization/overview.md b/docs/core/porting/github-copilot-app-modernization/overview.md index 428e40b279f13..ed1ac6b8f0368 100644 --- a/docs/core/porting/github-copilot-app-modernization/overview.md +++ b/docs/core/porting/github-copilot-app-modernization/overview.md @@ -137,7 +137,7 @@ Copilot examines your project structure, dependencies, and code patterns to buil - **Planning stage (`plan.md`)**\ Copilot converts the assessment into a detailed specification that explains how to resolve every problem. The plan documents upgrade strategies, refactoring approaches, dependency upgrade paths, and risk mitigations. -- **Execution stage (`tasks.md`)**\ +- **Execution stage (`progress.md`)**\ Copilot breaks the plan into sequential, concrete tasks with validation criteria. Each task describes a single change and how Copilot confirms it succeeded. Edit any of the Markdown files in `.github/upgrades` to adjust upgrade steps or add context before you move forward. @@ -150,7 +150,7 @@ When you reach the **Execution stage**, tell Copilot to start the upgrade. If Co ### Upgrade results -As Copilot runs each task, it updates the `tasks.md` file in `.github/upgrades` with the status of every step. Monitor progress by reviewing this file. The tool creates a Git commit for every portion of the process, so you can roll back changes or review what changed. +As Copilot runs each task, it updates the `progress.md` file in `.github/upgrades` with the status of every step. Monitor progress by reviewing this file. The tool creates a Git commit for every portion of the process, so you can roll back changes or review what changed. When the upgrade finishes, Copilot displays next steps in the chat response. From e69330e079f90a2aaeab78fb6190e255152834db Mon Sep 17 00:00:00 2001 From: ruchira-net <91104117+ruchira-net@users.noreply.github.com> Date: Tue, 31 Mar 2026 14:04:57 +1300 Subject: [PATCH 2/2] Update file references from tasks.md to progress.md --- .../how-to-upgrade-with-github-copilot.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/core/porting/github-copilot-app-modernization/how-to-upgrade-with-github-copilot.md b/docs/core/porting/github-copilot-app-modernization/how-to-upgrade-with-github-copilot.md index db0bbcc03f2f8..a7f48c0f94223 100644 --- a/docs/core/porting/github-copilot-app-modernization/how-to-upgrade-with-github-copilot.md +++ b/docs/core/porting/github-copilot-app-modernization/how-to-upgrade-with-github-copilot.md @@ -127,7 +127,7 @@ To review and customize the plan: ## Start execution and run the upgrade -The execution stage breaks the plan into sequential, concrete tasks with validation criteria. When you tell Copilot to proceed to execution, it generates a `tasks.md` file in `.github/upgrades/{scenarioId}`. +The execution stage breaks the plan into sequential, concrete tasks with validation criteria. When you tell Copilot to proceed to execution, it generates a `progress.md` file in `.github/upgrades/{scenarioId}`. The task list describes each task and how Copilot validates success. The following example shows the task list for a solution containing ASP.NET Core and WPF projects: @@ -181,7 +181,7 @@ This document tracks the execution of the MvcMovieNet6 solution upgrade from .NE To run the upgrade: 1. Tell Copilot to start the upgrade. -1. Monitor progress by reviewing the `tasks.md` file as Copilot updates task statuses. +1. Monitor progress by reviewing the `progress.md` file as Copilot updates task statuses. 1. If Copilot encounters a problem it can't resolve, provide the requested help. 1. Based on your decisions and changes, Copilot adapts its strategy to the remaining tasks and continues the upgrade. @@ -189,7 +189,7 @@ Copilot commits changes according to the Git strategy you configured during pre- ## Verify the upgrade -When the upgrade finishes, Copilot shows recommended next steps in the chat response. Review the `tasks.md` file in `.github/upgrades/{scenarioId}` for the status of every step. +When the upgrade finishes, Copilot shows recommended next steps in the chat response. Review the `progress.md` file in `.github/upgrades/{scenarioId}` for the status of every step. The following example shows completed tasks for an ASP.NET Core project upgrade: @@ -217,7 +217,7 @@ This document tracks the execution of the MvcMovieNet6 solution upgrade from .NE To verify the upgrade: -1. Review the final task status in `tasks.md`. +1. Review the final task status in `progress.md`. 1. Address any failing tests or compilation errors. 1. Ensure all updated NuGet packages are compatible with your application. 1. Test your application thoroughly to verify the upgrade succeeded.