chore: migrate cmd - reverse order of next steps when secrets detected

[andie787]

This PR changes the output of the depot ci migrate command:

• when secrets or variables are detected, the Next steps are reversed to suggest 1)importing secrets and vars 2) push and merge to default branch
• this means the first workflow run has a better chance of passing

---

Note

Low Risk
Low risk: only adjusts depot ci migrate console messaging/step numbering, with no changes to migration logic or API calls.

Overview
Updates depot ci migrate "Next steps" output so that when secrets/variables are detected it now instructs users to import secrets/vars first (step 1) and activate workflows by merging to the default branch second (step 2). When no secrets/vars are found, it prints only the activation instruction (without numbered steps).

^{Reviewed by Cursor Bugbot for commit 8963b45. Bugbot is set up for automated code reviews on this repo. Configure here.}

[graphite-app]

Missing step number prefix. When no secrets or variables are detected, the instruction should be numbered as step 1 for consistency with the other code path.

fmt.Fprintf(out, "  1. Activate these workflows by pushing and merging them into %s\n", bold.Render(defaultBranch))

Suggested change

	fmt.Fprintf(out, " Activate these workflows by pushing and merging them into %s\n", bold.Render(defaultBranch))
	fmt.Fprintf(out, " 1. Activate these workflows by pushing and merging them into %s\n", bold.Render(defaultBranch))

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.

[andie787]

disagree!