docs(sites): add deploy example to the root command - #138
Conversation
|
|
@codex review |
Greptile SummaryAdds Confidence Score: 5/5The PR appears safe to merge with no actionable defects identified. The new entry only extends the root command’s static examples with an existing sites deployment command, while the banner edits remove trailing whitespace without changing displayed content.
|
| Filename | Overview |
|---|---|
| packages/cli/src/cli.ts | Adds a valid static-site deployment example to the root landing page and performs non-functional whitespace cleanup. |
Reviews (1): Last reviewed commit: "docs(sites): add deploy example to the r..." | Re-trigger Greptile
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1ebee71c56
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ["Create an edge script", "bunny scripts init"], | ||
| ["Add a domain to manage DNS", "bunny dns zones add example.com"], | ||
| ["Create a dev sandbox", "bunny sandbox create my-sandbox"], | ||
| ["Deploy a static site", "bunny sites deploy"], |
There was a problem hiding this comment.
Keep experimental Sites off the landing page
When users run bunny without arguments, this row now advertises sites deploy even though sitesNamespace remains in experimentalCommands and is still defined as a hidden namespace. This exposes an experimental feature on the public landing page while it remains absent from normal help, creating an inconsistent release surface; remove the example until Sites is fully promoted.
AGENTS.md reference: AGENTS.md:L1107-L1107
Useful? React with 👍 / 👎.
No description provided.