Repository navigation
feat(cli): floo deploys and floo status --preview replace the history and preview inspection commands - #401
Conversation
…ases show `floo deploys [--app] [--env dev|prod|preview] [--limit] [--cursor]` is the one history command. A prod deploy shows the release it shipped: a Release column in the table, and a `release` object (tag, number, promoted_by, image) in --json. Only a page with a prod deploy fetches releases, so an app on dev alone sees no release column and pays no extra call. `floo deploys list`, `floo releases list` and `floo releases show` fail with COMMAND_REMOVED and name the replacement. The `releases` group is gone; `floo promote` already replaced `releases promote`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Eufw476uDAxxXQi632Y2Eq
…s resources `floo status --preview <branch>` shows a preview's latest deploy, URL and managed-resource branches (the old `previews status` plus `previews resources list`; --json carries every branch, so it covers `resources show`). `floo previews reset` replaces `previews resources reset`. previews keeps list, delete and reset. The removed commands fail with COMMAND_REMOVED and name the replacement. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Eufw476uDAxxXQi632Y2Eq
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 02f335d313
ℹ️ 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".
`floo logs build --follow` is build-logs' own flag, not the `--follow` alias of `floo logs --live`. The checker carried parent aliases into subcommands and rejected the docs' build-log examples. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Eufw476uDAxxXQi632Y2Eq
…ind their release An app with more than 100 releases lost the release tag on older prod deploys, because only the first release page was read. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Eufw476uDAxxXQi632Y2Eq
|
@codex review Generated by Claude Code |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
Summary
The last two folds from the deploy rework plan (epic getfloo/floo#4262, step 4):
floo deploysreplacesdeploys list,releases listandreleases show. It takes--env dev|prod|preview,--limitand--cursor. When a page holds prod deploys, each prod row shows the release it shipped: a Release column in the table and areleaseobject in JSON (tag, number, who promoted it, image).floo status --preview <branch>replacespreviews status,previews resources listandpreviews resources show. It shows the preview's deploy, URL and every managed resource branch (managed_resource_branchesin JSON).floo previewskeepslist,deleteandreset.previews reset <branch> --resource <key>replacespreviews resources reset(same flags, same preflight).Every removed command fails with
COMMAND_REMOVEDand names its replacement (src/commands/removed.rs).Issue Closure
Part of getfloo/floo#4262 (step 4). Does not close it.
Changes
Deploysis a leaf command with--app,--env,--limit,--cursor; thereleasesgroup is removed (floo promotealready replacedreleases promote);Statusgains--preview(conflicts with--commitand--wait);PreviewsSubcommandskeeps List, Delete, Reset.listtakesenv; prod rows join the app's releases (onelist_releasescall, only when a prod row is on the page; a failure warns and the list still prints).statuscarries the resource branches;resources_*removed,resources_resetis nowreset.promote.list_deploys_paginatedtakes an env filter; unusedget_releaseandget_preview_managed_resource_branchremoved.floo logs build --follow(build logs' own flag) is no longer flagged as the--followalias offloo logs --live. Found running the guidance check against the floo-docs sweep.Test Plan
cargo fmt --check,cargo clippy --all-targets -- -D warnings,cargo test(all pass locally).FLOO_EXTERNAL_GUIDANCE_DIR=<floo-docs sweep> cargo test --bin floo guidancepasses.test_deploys_prod_shows_the_release_each_deploy_shipped,test_deploys_without_a_prod_deploy_skips_releases(no releases call),test_status_preview_json_returns_all_managed_resource_branches,test_status_preview_resolves_preview_url_identifier,test_previews_reset_dry_run_and_yes_use_generic_endpoint.every_replacement_names_a_command_that_existschecks each removed path no longer parses and each replacement exists.Discovered Issues
None new. The floo API hints, knowledge base and docs site follow in their own PRs once this merges.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Eufw476uDAxxXQi632Y2Eq