[devin-ai-integration]

• In merge queue / Merged
• Prioritize

Summary

Documents two changes to pipeline sandbox steps:

• Shared build cache: steps with a git source automatically use the shared build cache. Go uses it through GOCACHEPROG, and Rust through sccache when the step already uses it. Entries are scoped to the repository and branch, fall back to the default branch, and are shared with the repository's GitHub Actions jobs. Your own settings win, and RAVION_GO_CACHE_PROG=off / RAVION_SCCACHE=off turn it off.
• Disk saves on failure: a step saves its disk when it succeeds or when one of its commands fails. It doesn't save when it's cancelled, times out, runs out of disk, or loses its host.

Pages: concepts/sandboxes.mdx (new "Shared build cache for pipeline steps" section, save rules updated) and a cross-link in github-actions/caching.mdx.

Merge after the matching ravionhq/flightcontrol change ships.

Link to Devin session: https://app.devin.ai/sessions/b7b4d566dd444445a1c4d921274ec62c
Open in Devin Desktop: https://app.devin.ai/desktop/session/b7b4d566dd444445a1c4d921274ec62c?variant=devin

Confidence Score: 4/5

The PR appears safe to merge, with two non-blocking documentation fixes.

Findings

1.  Disk save rules disagree ▶
2.  Disk reset guidance is misplaced ▶

Fix with agent prompt

### Issue 1
concepts/sandboxes.mdx:344
The new save rule includes failed steps, but the `disk_cache` reference still says “The last green run to finish publishes it.” Users get different answers about whether failed steps replace the saved disk. Update the configuration reference alongside this page.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

### Issue 2
concepts/sandboxes.mdx:348
This heading puts the existing `--no-cache` instructions inside the shared build cache section. The flag clears saved disks, not the independent shared build cache. Readers may clear their disk while expecting to bypass Go or Rust cache entries. Move the new section below the existing cleanup guidance.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Documents shared build caching and disk saves after failed pipeline commands.

• Sandbox docs explain when failed steps save their disks.
• Pipeline docs explain how steps share Go and Rust build caches.

Reviews (1) · Last reviewed commit: "Document pipeline sandbox build cache" · Reviewed by Greptile

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Ravion	🟢 Ready	View Preview	Oct 23, 2026, 12:23 AM