Skip to main content
Every completed milestone produces a Pull Request in your GitHub repository. This is your checkpoint—the moment to verify that the migrated code meets your expectations before it becomes part of your codebase.

​
Why PRs Matter

The Pull Request is your safeguard. It ensures:
  • No blind merges — You see every line of generated code
  • Normal workflow — Uses the same review process as any other PR
  • Team involvement — Other reviewers can participate
  • CI/CD validation — Your existing pipelines run against the changes

​
Opening a Milestone PR

When a milestone’s tasks complete:
  1. An alert appears: “Pull request is ready for review”
  2. Click Review Pull Request
  3. The PR opens in a new GitHub tab

​
What to Review

​
Code Quality

  • Does the generated code follow good practices?
  • Are there any obvious bugs or issues?
  • Is the code readable and maintainable?

​
Correctness

  • Does the migration preserve the original functionality?
  • Are edge cases handled?
  • Do the transformations make sense?

​
Consistency

  • Does the code match your team’s conventions?
  • Are naming patterns consistent with existing code?
  • Is the style what you expected?

​
Tests

  • Were tests migrated or generated?
  • Do they cover the key functionality?
  • Do they pass?

​
Taking Action

​
If Everything Looks Good

  1. Approve the PR in GitHub
  2. Merge using your preferred strategy (merge commit, squash, rebase)
  3. Return to —the milestone status updates to Merged
  4. The next milestone unlocks

​
If You Find Issues

You have several options: Make Manual Fixes The PR is a standard GitHub Pull Request. You can:
  • Push additional commits to fix issues
  • Edit files directly in GitHub
  • Clone locally and push changes
Once your fixes are in, merge as normal. Request Regeneration For significant issues, you might want to try again:
  1. Close the PR without merging
  2. In , the milestone returns to a state where you can retry
  3. Consider editing the milestone before regenerating
Create Rules for Future Milestones If the issue is a pattern (e.g., wrong naming convention), create a Rule to prevent it in subsequent milestones.

​
If Checks Fail

CI/CD checks run on PRs automatically. If they fail:
  1. Click into the failed check in GitHub
  2. Review the failure reason
  3. Common causes:
    • Linting violations (may need style adjustments)
    • Test failures (tests may need updates for new code)
    • Build errors (configuration may need tweaks)
  4. Fix the issues and push updates
  5. Merge once checks pass

​
PR States in

The milestone status reflects the PR state:
StatusPR State
Pending ReviewPR open, awaiting review
Pending Review (with warning)PR checks failed
MergedPR merged into target branch
automatically detects when you merge, updating the milestone status.

​
Best Practices

​
Review Promptly

Don’t let PRs sit. The next milestone is blocked until you merge. Review and merge (or address issues) to keep momentum.

​
Use Your Normal Process

Treat milestone PRs like any other PR:
  • Add reviewers if your team normally does
  • Require approval if that’s your policy
  • Run additional manual tests if needed
When reviewing, consider:
  • Do changes in this milestone connect properly to previous milestones?
  • Are there any inconsistencies with already-merged code?

​
Document Decisions

If you make manual changes to a PR before merging, consider noting why. This helps if similar issues come up in later milestones.

​
After Merging

Once merged:
  1. The milestone shows Merged status
  2. The next milestone becomes available
  3. Repeat the process: Review → Generate → Execute → Review PR → Merge
When all milestones are merged, your migration is complete.

​
Troubleshooting

​
”PR was closed without merging”

If you accidentally close a PR:
  1. Reopen it in GitHub, or
  2. In , retry the milestone to generate a new PR

​
”Merge conflicts”

Conflicts can occur if:
  • You made manual changes to the repository
  • Another branch was merged between milestones
Resolve conflicts in GitHub as you normally would, then merge.

​
”PR stuck in pending state”

If doesn’t detect your merge:
  1. Refresh page
  2. Check that the PR is actually merged in GitHub
  3. Wait a moment—status updates poll periodically
  4. Contact support if the issue persists