Why Milestones Matter
Progressive Change
Each milestone builds on the previous one. This means:- Changes are incremental and reviewable
- You can catch issues early, before they compound
- The codebase stays in a working state after each milestone
You Stay in Control
Every milestone produces a Pull Request. You:- Review the changes
- Run your own tests if needed
- Merge when satisfied
Logical Grouping
Milestones aren’t random file splits. They represent logical units of work:- Related files are migrated together
- Dependencies are respected
- Each milestone makes sense as a standalone change
The Three-Step Milestone Process
Each milestone follows three steps:Step 1: Review the Milestone
Before any code is generated, understand what the milestone will accomplish:- Click on a milestone to expand it
- Click Review to open the milestone details
- Read the description of what will be migrated
- Check the list of relevant files
Step 2: Generate Tasks
With the milestone understood, generate the specific work items:- Click Generate Tasks
- Wait for task planning to complete
- View the generated tasks in the Tasks tab
Step 3: Execute Tasks
Run the migration for this milestone:- Click Execute Tasks
- Watch progress as each task completes
- When finished, a Pull Request is automatically created
Reviewing the Pull Request
Every completed milestone produces a PR in your GitHub repository:- Click Review Pull Request to open it in GitHub
- Review the code changes as you would any PR
- Run tests, leave comments, request changes if needed
- Merge when satisfied
Why Milestones Are Sequential
Milestones must be completed in order because each one builds on the previous:- Milestone 2 assumes Milestone 1’s changes exist
- Later milestones may reference files created by earlier ones
- The migration sequence is designed to avoid breaking changes
Milestone Statuses
| Status | Meaning |
|---|---|
| Not Started | Ready to begin when prior milestones are complete |
| In Progress | Tasks are currently executing |
| Pending Review | PR is ready for your review |
| Merged | You’ve merged the PR; milestone complete |
| Failed | An error occurred; see troubleshooting |
When Things Go Wrong
Task Execution Failed
If tasks fail during execution:- Expand the milestone to see which task failed
- Review the error message
- Click Retry Execute to try again
- If failures persist, see Troubleshooting
PR Generation Failed
If the PR couldn’t be created:- Click Retry PR
- Check your GitHub permissions if it fails again
- Contact support if the issue persists
PR Review Checks Failed
If your CI/CD checks fail on the PR:- Review which checks failed in GitHub
- Make manual fixes if needed
- The PR is a standard GitHub PR—you can push additional commits
Tips for Smooth Milestones
Review Before Generating
Take time to review the milestone description before generating tasks. If something looks wrong, you can edit it before proceeding.Don’t Rush Merges
Review PRs carefully. It’s easier to catch issues now than to fix them after several more milestones have built on top.Use Rules for Recurring Issues
If you notice making the same mistake across milestones, create a Rule to prevent it in future milestones.One Milestone at a Time
Complete each milestone before starting the next. This ensures:- Changes are properly integrated
- Issues are caught early
- The codebase stays consistent
Next Steps
- Reviewing Pull Requests — Best practices for PR review
- Editing Milestones — Adjust before generating
- Creating Rules — Encode preferences for better results