For Training

Audience: Dentolize engineers and reviewers who'll actually use /sandbox day to day. This is a short how-to, not a conceptual deep dive — see Feature breakdown for the mechanics.

Getting a sandbox for your own PR (or one you're reviewing)

1. Open the pull request on GitHub.
2. Comment /sandbox.
3. Watch for the 👀 reaction (comment received), then 🚀 (dispatched

successfully) or 😕 (typo/unrecognized command) or 👎 (you don't have write access — ask someone who does).

1. Wait for the separate sandbox-info comment to appear/update on the PR —

that's Sandbox Ops finishing, usually within a couple of minutes. It has the web URL and every seeded login (owner, doctors, receptionist, accountant, HR manager — same password for all of them).

1. Open the web URL and log in with any of the seeded users to review the

change live.

The other commands, when to use them

• /sandbox reseed — if login stopped working (password or 2FA got out

of sync) but you don't need to lose test data you've added.

• /sandbox reset-data — if the data in the sandbox got messy or

corrupted during testing and you want a clean slate. Uploaded files survive; everything else is wiped and reseeded.

• /sandbox destroy — if you're done reviewing early and want to free

up the sandbox before the PR closes (it auto-destroys on close/merge anyway).

• /sandbox docs — regenerates this documentation site for the PR's

branch. This can take a while (up to ~90 minutes if it also needs to stand up a missing sandbox first) and runs in the foreground of its own Actions job, so you can watch progress there.

Checking what's currently deployed

Don't go hunting in the Actions tab. Open the pinned 🗂 Open sandboxes issue (top of the repo's Issues list) — it lists every live sandbox with status, branch, linked PR, web link, commit, and how long ago it deployed. It refreshes itself; you never need to manually update it.

Common mistake to avoid

Don't confuse /sandbox (this PR) with editing the ## 🧪 Sandbox block in the PR description (#428, still supported) — they both end up dispatching work, but the PR-body block controls settings for the automatic deploy that happens on every commit, while /sandbox is an on-demand trigger for the same underlying Sandbox Ops actions. Editing the PR body without changing that block does not trigger a redeploy on its own.