Skip to content

docs(providers): correct provider lifecycle commands and desktop controls - #1629

Merged
skevetter merged 3 commits into
mainfrom
docs/maintenance-provider-management-20261020
Oct 20, 2026
Merged

skevetter merged 3 commits into
mainfrom
docs/maintenance-provider-management-20261020

Conversation

@skevetter

@skevetter skevetter commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Corrects manage-providers.mdx claims the source contradicts. Docs only, one file.

  • devsy up --recreate -> devsy workspace up <name> --recreate (no top-level devsy up).
  • Workspaces reference a provider by name, not a version. Lookup is FindProvider (pkg/workspace/provider.go).
  • Desktop: Delete button with confirmation; inline Rename button (ProviderSheet.svelte).
  • Rename: "Platform providers" cannot be renamed; renaming can stop running workspaces (SwitchProvider).

Why

The page named a command that does not exist, described a version pin the code does not implement, and documented desktop controls not in the UI.

Validation

  • Coordinator reviewed every hunk against source.
  • origin/main merged (signed, ordinary merge, 4107c5fdb); no rebase, no force.
  • Diff vs base: 7 added, 7 removed (14 changed lines), one file.
  • npm run build in sites/docs-devsy-sh: pass.
  • npm run check-links: 0 errors.
  • Biome does not parse .mdx; no lint gate applies.

CodeRabbit CLI

coderabbit review --agent --committed --fresh --base-commit $(git merge-base HEAD origin/main) on bcbb82e2: rate limited (free OSS quota) on four attempts; last reported wait 3 minutes. Logs: /tmp/coderabbit-bcbb82e2.jsonl, -retry.jsonl, -final.jsonl, -after-wait.jsonl. Last completed fresh run, on 4aa2cc8f, found 0 issues. Not run on bcbb82e2. GitHub CodeRabbit review on this head is complete with zero actionable findings.

Auto-merge

Eligible: content-only, under 300 lines, no lockfile or package.json change. Gated on CI and reviews.

AI and testing

  • AI: yes. omp, anthropic/claude-haiku-5-5, drafted edits and checked claims.
  • Testing: no integration test needed; docs only. Site build and link check cover the page.
  • CLA: green.

@skevetter skevetter added the docs-cleanup Docs cleanup (maintenance bot) label Oct 20, 2026
@netlify

netlify Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for devsydev canceled.

Name Link
🔨 Latest commit bcbb82e
🔍 Latest deploy log https://app.netlify.com/projects/devsydev/deploys/6ad7ea28024691e22f380cde

@coderabbitai

coderabbitai Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

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: 4a9e5a9a-f17e-44bf-ab13-0d0d026ac6a9
📥 Commits

Reviewing files that changed from the base of the PR and between 4107c5f and bcbb82e.

📒 Files selected for processing: 1
  • sites/docs-devsy-sh/content/docs/managing-providers/manage-providers.mdx

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

📝 Walkthrough

The provider management documentation updates the MicroSandbox VM recreation command and revises guidance on provider lookup, deletion, and renaming.

Changes: Provider management documentation

Layer / File(s) Summary
Workspace recreation command
sites/docs-devsy-sh/content/docs/managing-providers/manage-providers.mdx
The MicroSandbox VM recreation example now uses devsy workspace up <name> --recreate.
Provider lookup and lifecycle guidance
sites/docs-devsy-sh/content/docs/managing-providers/manage-providers.mdx
The documentation says workspaces resolve providers by name when loaded. It updates deletion restrictions and renaming rules, including the effect renaming may have on running workspaces.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to bcbb8

This documentation-only change is ready to merge; its updated guidance matches the referenced behavior.

Architecture risk: 🔵 Low · up to bcbb8

The change affects 1 system.

Changed systems: sites

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — sites (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in sites/docs-devsy-sh/content/docs/managing-providers/manage-providers.mdx: Updated the MicroSandbox VM recreation command from devsy up --recreate to devsy workspace up <name> --recreate.
  • observed — Modified behavior in sites/docs-devsy-sh/content/docs/managing-providers/manage-providers.mdx: Replaced the statement that existing workspaces pin their creation-time provider version with documentation that workspaces resolve providers by name when loaded.
  • observed — Modified behavior in sites/docs-devsy-sh/content/docs/managing-providers/manage-providers.mdx: Updated provider deletion guidance: the Desktop action is now Delete with confirmation, deletion fails while a workspace uses the provider, and the warning states that the CLI refuses deletion rather than leaving workspaces unusable until the provider is restored.
  • observed — Modified behavior in sites/docs-devsy-sh/content/docs/managing-providers/manage-providers.mdx: Renaming is now prohibited for platform providers instead of Pro providers, may stop running workspaces that use the provider, and uses the Desktop Rename action instead of editing Provider Name and updating options. The prior instruction to stop workspaces first was removed.
Pre-merge checks: Passed 4 · Failed 1

Failed Failed checks: 1 warning

Check name Status Explanation Resolution
Description check Warning The description explains the documentation changes, rationale, AI use, and validation results. It does not follow the repository template and omits the required Type of change, Fixes/Refs, structured … Rewrite the description using the repository template. Add the What and why section with Fixes #N or Refs #N (or none), select Docs under Type of change, complete the AI assistance fields and confirmations, document that no integratio…
Passed Passed checks: 4 passed
Check name Status Explanation
Title check Passed The title clearly identifies the documentation change and its provider lifecycle and desktop-control scope.
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 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

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 0 files. (1 skipped: 1 unsupported.)

Full details: Description check

Explanation

The description explains the documentation changes, rationale, AI use, and validation results. It does not follow the repository template and omits the required Type of change, Fixes/Refs, structured AI assistance, Testing, Checklist, and Notes for reviewers sections.

Resolution

Rewrite the description using the repository template. Add the What and why section with Fixes #N or Refs #N (or none), select Docs under Type of change, complete the AI assistance fields and confirmations, document that no integration test is needed because this is a docs-only change, record the validation commands, and complete the applicable Checklist items.

✨ Finishing Touches
✨ Simplify code
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@netlify

netlify Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for images-devsy-sh canceled.

Name Link
🔨 Latest commit bcbb82e
🔍 Latest deploy log https://app.netlify.com/projects/images-devsy-sh/deploys/6ad7ea2861078edd8a456d6f

@skevetter
skevetter marked this pull request as ready for review October 20, 2026 22:38
@skevetter

Copy link
Copy Markdown
Contributor Author

@greptileai review

@mergify

mergify Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.

@greptile-apps

greptile-apps Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] This documentation-only PR appears safe to merge.

Summary

Corrects provider lifecycle instructions in manage-providers.mdx.

  • The guide points readers to the workspace recreate command.
  • Workspaces use a provider name, not a saved provider version.
  • People confirm provider deletion in Desktop, and the CLI blocks providers in use.
  • Desktop users rename providers with the Rename control.

No actionable issues found.

Reviews (1) · Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." · Reviewed by Greptile

@skevetter

Copy link
Copy Markdown
Contributor Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
✅ Action performed

Full review finished.

@skevetter
skevetter merged commit ec3619a into main Oct 20, 2026
37 checks passed
@skevetter
skevetter deleted the docs/maintenance-provider-management-20261020 branch October 20, 2026 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-cleanup Docs cleanup (maintenance bot) size/xs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant