Skip to content

docs(provider): distinguish source previews from releases - #1763

Merged
skevetter merged 1 commit into
mainfrom
docs/docker-sandbox-preview-availability
Nov 4, 2026
Merged

skevetter merged 1 commit into
mainfrom
docs/docker-sandbox-preview-availability

Conversation

@skevetter

@skevetter skevetter commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Cause

The provider guide says no release exists. A source-only preview must not be confused with a qualified, installable release.

Fix

Describe preview source archives separately from the provider manifest and supported host claims. Keep installation instructions conditional on native qualification.

Test evidence

Commit: 4c5c219202ab3e2eaf39050fdf9783b0ea63730b. git diff --check: 0 errors. CI: 18 pass, 6 neutral, 9 skipped, 0 failures or pending. The Netlify preview rendered the updated release notice; a browser screenshot was captured. No behavior code changed.

Not verified

Live Docker Sandboxes, native VM qualification, and deployment are not verified. The local mise exec -- prek run --all-files timed out during another worktree's lint run; GitHub's pre-commit job passed.

@netlify

netlify Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for images-devsy-sh canceled.

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

@netlify

netlify Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for devsydev ready!

Name Link
🔨 Latest commit 4c5c219
🔍 Latest deploy log https://app.netlify.com/projects/devsydev/deploys/6aeab916325336a58f299d64
😎 Deploy Preview https://deploy-preview-1763--devsydev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Walkthrough

The Docker Sandboxes provider notice now distinguishes source-only previews from installable releases. It states that installation and machine instructions apply only to a natively qualified, published installable release.

Changes: Docker Sandboxes documentation

Layer / File(s) Summary
Clarify preview and release requirements
sites/docs-devsy-sh/content/docs/managing-providers/docker-sandbox.mdx
The notice states that a source-only preview has no installable manifest or supported-host claim. Installation and machine instructions apply only after native qualification and publication of an installable release.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Possibly related issues

Possibly related PRs

  • devsy-org/devsy#1753: Both changes document Docker Sandboxes release and host qualification requirements.
  • devsy-org/devsy#1749: Both changes address the Docker Sandboxes guide’s release and installation contract.

Suggested labels: size/xs, docs-cleanup

Merge Risk: Minimal · up to 4c5c2

The notice clarifies that source-only previews are not installable releases. No merge-blocking risk is identified in this documentation-only change.

Pre-merge checks: Passed 3 · Failed 1

Failed Failed checks: 1 warning

Check name Status Explanation Resolution
Description check Warning The description states the cause (the provider guide says no release exists, so source-only previews can be confused with installable releases), the fix (preview source archives are described separate… Complete the template sections the description omits: (1) Add an issue reference line, using 'Fixes #N' or 'Refs #N', or write 'none' if there is no issue. (2) Under 'Type of change', tick 'Docs'. (3) Under 'AI assistance', tick either 'No …
Passed Passed checks: 3 passed
Check name Status Explanation
Title check Passed The title clearly identifies the documentation change: distinguishing provider source previews from installable releases. It is concise and directly related to the main change.
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: Description check

Explanation

The description states the cause (the provider guide says no release exists, so source-only previews can be confused with installable releases), the fix (preview source archives are described separately from the provider manifest and supported-host claims, with installation conditional on native qualification), and test evidence (commit hash, git diff --check with 0 errors, CI results, Netlify preview rendering with a screenshot, no behavior code changed). It also has a Not verified section. However, it does not follow the required template: it has no Conventional Commits title in the template form, no 'What and why' heading, no 'Fixes #' or 'Refs #' issue line, no 'Type of change' selection (the change is docs, but it is not ticked), no 'AI assistance' section, no testing checkboxes stating whether an integration test is needed (it should name that docs-only changes need no e2e test), and no checklist items such as lint and CLA confirmation. The core content is solid, but several required template sections are missing.

Resolution

Complete the template sections the description omits: (1) Add an issue reference line, using 'Fixes #N' or 'Refs #N', or write 'none' if there is no issue. (2) Under 'Type of change', tick 'Docs'. (3) Under 'AI assistance', tick either 'No AI tools were used' or 'AI tools were used' and fill in the table, or state that none were used. (4) Under 'Testing', tick 'No integration test needed, because: docs only' and name the reason. (5) Complete the 'Checklist' items that apply, such as confirming the docs under sites/ are updated, that no secrets or personal paths are present, and that the CLA is signed. (6) Remove any template comments and leave no placeholders. (7) Keep the existing 'Not verified' content, and place it under 'Notes for reviewers' if you want a separate section.

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
Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f4c7b927-a98a-4b34-8683-0a00bc6189be
Commits

Reviewing files that changed from the base of the PR and between d344603 and 4c5c219.

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

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

@mergify

mergify Bot commented Nov 4, 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.

@skevetter

Copy link
Copy Markdown
Contributor Author

@greptileai review

@greptile-apps

greptile-apps Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The documentation change appears safe to merge.

Summary

Clarifies the difference between Docker Sandboxes source previews and qualified releases.

  • The Docker Sandboxes guide separates source previews from qualified releases.

Reviews (1) · Last reviewed commit: "docs(provider): distinguish source previ..." · Reviewed by Greptile

@skevetter
skevetter merged commit b2024b2 into main Nov 4, 2026
36 checks passed
@skevetter
skevetter deleted the docs/docker-sandbox-preview-availability branch November 4, 2026 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant