Rename tasks.md to progress.md in overview.md#52712
Rename tasks.md to progress.md in overview.md#52712ruchira-net wants to merge 1 commit intodotnet:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Updates GitHub Copilot modernization for .NET documentation to reference progress.md (instead of tasks.md) as the execution-stage tracking file under .github/upgrades.
Changes:
- Rename the execution-stage file reference from
tasks.mdtoprogress.md. - Update the “Upgrade results” section to point readers to
progress.mdfor status tracking.
| - **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. | ||
|
|
There was a problem hiding this comment.
The doc now says the execution stage generates/updates progress.md, but other GitHub Copilot modernization for .NET docs in the same directory still describe a tasks.md file for execution (for example, how-to-upgrade-with-github-copilot.md and how-to-custom-upgrade-instructions.md). Please align the file name across the doc set (either revert to tasks.md here, or update the other pages in the same PR) so readers don't follow conflicting instructions.
| ### 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. |
There was a problem hiding this comment.
This paragraph references progress.md as the status tracker, but the rest of the GitHub Copilot modernization for .NET upgrade workflow docs currently instruct users to monitor tasks.md. Confirm which filename the product actually writes under .github/upgrades and update the docs consistently to avoid sending users to a non-existent file.
Summary
I don't think the file is called tasks.md any longer. Now it's been renamed to progress.md
Fixes #Issue_Number (if available)
Internal previews