Caching
actions/cache and the tools built on it (setup-node, setup-python,
rust-cache, …) work unchanged, with GitHub’s scoping: a push saves to its
branch; a pull request saves to itself and reads its own caches, then its base
branch’s, then the default branch’s. Caches never cross repositories.
- By default they are GitHub’s Actions caches of your repository, as on any runner.
- With Darkbloom’s build cache (enabled per repository by Darkbloom), they are stored encrypted on the Mac that saved them instead, and restore at disk speed. A job placed on another Mac misses, and pull requests from forks get none.
Network
A job reaches the network over outbound HTTPS only, through Darkbloom’s gateway, and only to hosts on the repository’s list:- GitHub’s published Actions hosts (checkout, actions, caches, artifacts, releases);
- the hosts Darkbloom reviewed for your repository (package registries, model hubs).

