[jacobwg]

We actually briefly entertained the idea of adding GitHub Runners as well. :) Perhaps someday, but we have a long way to go just on just Docker / containers.

Just to note, you can totally use Depot within your GitHub Actions runs, even if those runs are happening inside self-hosted or BuildJet-hosted runners. You might get the best of both worlds that way, having your builds and tests outside of Docker run on BuildJet, and Docker builds accelerated with Depot.

[Serow225]

Thanks! Maybe it would be worth adding a docs example of a proper GH workflow using Depot?

It’s a decent option, but it’s still more complicated (multiple vendors, configuration, etc)

You know what, it could be really nice if y’all could create a simple Depot GH Action that would make things more efficient (for example pass in the repo token so that Depot could pull the repo vs first pulling it from GH into the workflow runner and then ship it over Depot)

[jacobwg]

The docs can be improved, but here's the GitHub Actions guide: https://depot.dev/docs/integrations/github-actions

The most important bit though is that we have a `depot/build-push-action` that implements the same inputs as Docker's `docker/build-push-action`, so just swapping that line and adding a project ID and access token are the majority of what you'd need to do:

      - uses: depot/setup-action@v1
      - uses: depot/build-push-action@v1
        with:
          project: <your-depot-project-id>
          token: ${{ secrets.DEPOT_TOKEN }}

          # Whatever other inputs:
          context: .
          push: true
          tags: |
            ...

I think that's along the lines of what you're describing as a Depot GitHub Action: https://github.com/depot/build-push-action.

[Serow225]

Thanks! I missed seeing that on your site.