---------------------- Based on the knowledge sources provided, I can see that Garden has built-in caching mechanisms, but I don't find specific information about integrating with GitHub's build cache directly. Here's what Garden offers for caching in CI environments: ## Garden's Built-in Caching Garden provides several caching mechanisms that work in CI: 1. **Team Caching**: Garden automatically caches build and test results that can be shared across your team and CI runs. When you connect your project to [Garden Cloud](), caching is enabled automatically. This means if someone on your team or a previous CI run has already built something, subsequent builds can reuse those results. [Team Caching]() 2. **Cluster BuildKit Cache**: For Kubernetes-based builds, Garden uses BuildKit with registry-based caching by default. The configuration looks like this:

clusterBuildkit:
  cache:
    - type: registry
      mode: auto

This automatically imports cached layers from a Docker image tag named

_buildcache

and uploads cache information after builds complete. [Configuration reference]() 3. **Remote Container Builder**: Garden includes a Remote Container Builder that builds containers faster and caches results, so actions don't run unless they need to. [Garden Basics]() ## GitHub Build Cache Integration The knowledge sources do not explicitly mention integration with GitHub's native build cache for

garden build

and

garden publish

commands. Garden appears to rely on its own caching mechanisms (Team Caching and registry-based BuildKit caching) rather than GitHub Actions' cache.

message has been deleted

For the fastest CI builds, you would want to ensure you have [Team Caching enabled by connecting to Garden Cloud]() and properly configure the BuildKit registry cache. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------