Skip to content

docs(sites): correct the command reference and agent skill - #249

Merged
jamie-at-bunny merged 2 commits into
mainfrom
sites-docs
Oct 8, 2026
Merged

jamie-at-bunny merged 2 commits into
mainfrom
sites-docs

Conversation

@jamie-at-bunny

Copy link
Copy Markdown
Member

Corrects the bunny sites command reference and agent skill.

@changeset-bot

changeset-bot Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 9bd040f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages
Name Type
@bunny.net/cli Patch
@bunny.net/cli-darwin-arm64 Patch
@bunny.net/cli-darwin-x64 Patch
@bunny.net/cli-linux-arm64 Patch
@bunny.net/cli-linux-x64 Patch
@bunny.net/cli-windows-x64 Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@bunnynet-devops

Copy link
Copy Markdown

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-07T16:24:51.865821Z 8faca51 Manual request
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8faca51c33

ℹ️ 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".

Comment thread skills/bunny-cli/references/sites.md Outdated
- Pass `--force` on anything with a confirmation (publish, prune, remove, delete, `create --from-zone`); without a TTY they error with a hint rather than waiting on a prompt.
- Pass the site explicitly (or commit `bunny.jsonc` with `sites.name`); the interactive picker is disabled under `--output json` and by `--force`, so `sites delete --force` with nothing linked errors instead of prompting.
- `--output json` on every command emits machine-readable results. `deploy` prints `{ id, production, unchanged, live }`, where `production` is `null` on a site whose hostname couldn't be read.
- `--output json` on every command emits machine-readable results. `deploy` prints `{ site, id, source, files, bytes, production, unchanged, live }`, where `production` is `null` on a site whose hostname couldn't be read.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Account for unchanged deploys in the documented JSON shape

When sites deploy --output json redeploys content that is already live, the handler returns early with only site, id, unchanged, live, and production; source, files, and bytes are absent. This skill now promises those fields for every deploy result, so agents can mis-handle this common no-op response; document the conditional fields or make the payload consistent.

Useful? React with 👍 / 👎.

Comment thread packages/cli/README.md Outdated
| `--previous` | `deployments publish` | Publish the previous deploy (instant rollback) |
| `--keep` | `deployments prune` | Number of recent deploys to keep (default 5; live and previous are always kept) |
| `--ssl`, `--wait`, `--force-ssl` | `domains add` | Issue SSL now; wait up to 10 minutes for DNS then issue it; `--no-force-ssl` keeps HTTP working |
| `--force-ssl` | `ssl`, `domains ssl` | Force HTTP→HTTPS on the system host; `--no-force-ssl` allows plain HTTP |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Describe domains SSL as acting on the custom domain

For bunny sites domains ssl <domain>, --force-ssl controls HTTP-to-HTTPS redirection on the named custom domain; only the top-level bunny sites ssl command operates on the system hostname. Adding domains ssl to this row while retaining “on the system host” misdocuments the command's target, so split the entries or generalize the description.

AGENTS.md reference: AGENTS.md:L3-L5

Useful? React with 👍 / 👎.

@greptile-apps

greptile-apps Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 5/5

[Low risk] Documentation corrections for the sites command reference.

The documentation changes appear safe to merge.

Summary

Corrects the bunny sites command reference and agent skill.

  • Adds missing flags and corrects which commands accept --site and --link.
  • Narrows the documented deploy output to fields shared by both successful paths.
  • Removes the incorrect system-host description for domains ssl.
  • Both previous findings are addressed. No new actionable issues were found.

Reviews (2) · Last reviewed commit: "docs(sites): fix the domains ssl row and..." · Reviewed by Greptile

Comment thread skills/bunny-cli/references/sites.md Outdated
Comment thread packages/cli/README.md Outdated
@jamie-at-bunny
jamie-at-bunny merged commit b7b028f into main Oct 8, 2026
6 checks passed
@jamie-at-bunny
jamie-at-bunny deleted the sites-docs branch October 8, 2026 10:07
@github-actions github-actions Bot mentioned this pull request Oct 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants