[quicksilversel]

Why

Two states around the Console's repository connection are hard to decode from the outside. The Console's setup job can fail at its install step (it resolves dependencies from scratch, so a peer-dependency conflict a committed lockfile would avoid can break it), and when it does, the pull request that would have added the Quick-start workflow never appears and nothing points back at this action. The Console then shows "Waiting for GitHub to start the first deployment", which reads as if pushing will fix it, but no push helps until a workflow with this action exists on the branch.

Change

A Troubleshooting section in the README, between Known limitations and Security, covering both states. Docs only.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: f5261f60-a12b-42f4-9fb3-873f68cb34c8

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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