Stop init from crashing when the team list is empty

[Hashim1999164]

Fixes #8355

netlify init with the manual flag asks for a team through an inquirer list. When the account list is empty that prompt reads value on undefined and the command crashes.

The non interactive path already reports that there are no teams. Interactive project create now checks that first so it exits with the same message instead of opening an empty list.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: f3d3d2cd-adaf-4ec2-8185-234ea2d8dc7d

📥 Commits

Reviewing files that changed from the base of the PR and between 2c4c744 and d7880fa.

📒 Files selected for processing (2)

• src/commands/sites/sites-create.ts
• tests/unit/commands/sites/sites-create.test.ts

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• netlify/blueprints (manual)

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Summary

Summary by CodeRabbit

• Bug Fixes
  • Interactive site creation now reports a clear “No teams available” error when no teams can be selected, instead of opening a team prompt.
  • Team selection validates that teams are available before proceeding, including when teams are missing or the list is empty.
  • Non-interactive team selection also reports an error when no teams are available.

Walkthrough

The change adds requireTeams to reject missing or empty account lists with the existing “No teams available” error. Non-interactive team resolution uses the helper. Interactive site creation validates accounts before opening the team prompt. Unit tests cover validation, team resolution, and the no-accounts interactive path.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix · Severity of issue fixed: Medium

Suggested reviewers: jherr

Merge Risk: ⚪ Minimal · up to d7880

The empty-team path is guarded before the prompt opens. No actionable merge risk remains beyond normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: preventing netlify init --manual from crashing when no teams are available.
Description check	✅ Passed	The description accurately explains the empty-team failure, the interactive prompt issue, and the guard added to match the non-interactive behavior.
Linked Issues check	✅ Passed	Issue [#8355] requires netlify init --manual to handle an empty team list without opening an empty selection prompt. sitesCreate calls requireTeams before the interactive selector. `requireTeams…
Out of Scope Changes check	✅ Passed	The changes stay within issue [#8355]. The shared requireTeams helper and the non-interactive refactor centralize existing empty-team validation. The added tests cover the interactive regression and…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 4…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}

[Hashim1999164]

rebased onto latest main. the empty team list guard is wired through the new @inquirer/prompts select path now.