Skip to content

Rename tasks.md to progress.md in overview.md #52712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ruchira-net wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Rename tasks.md to progress.md in overview.md #52712

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/core/porting/github-copilot-app-modernization/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Comment on lines +140 to 142
Copy link

Copilot AI Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
Edit any of the Markdown files in `.github/upgrades` to adjust upgrade steps or add context before you move forward.
Expand All @@ -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.
Copy link

Copilot AI Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.

When the upgrade finishes, Copilot displays next steps in the chat response.

Expand Down
Loading