# depot/build-push-action GitHub Action (https://depot.dev/changelog/2022-05-16-build-push-action)

> Published 2022-05-16

We wanted to make it simple to try Depot in your existing GitHub Action workflows. So, we released [`depot/build-push-action`](https://github.com/depot/build-push-action), that implements the same inputs and outputs as `docker/build-push-action` but makes uses of our `depot` CLI to run your build.

**Bonus: We now support OIDC token authentication in GitHub Actions 🎉**

Our new GitHub Action also allows you to use [GitHub's OIDC token](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect) as authentication to `depot build`. No more static access keys in GitHub Actions!

If you set the `permissions` block in your action workflow and make use of `depot/build-push-action` you can authenticate builds via OIDC and don't need to generate a user access token.

```yaml
jobs:
  build:
    runs-on: ubuntu-20.04
    permissions:
      contents: read
      id-token: write
    steps:
      - uses: actions/checkout@v3
      # The depot CLI still needs to be available in your workflow
      - uses: depot/setup-action@v1
      - uses: depot/build-push-action@v1
        with:
          context: .
          push: true
```

If you want to see an example of this new authentication method in action, you can check out our [`moby/moby` benchmark workflow](https://github.com/depot/benchmark-moby/blob/main/.github/workflows/benchmark.yml).

## For AI Agents

The full site index is at [llms.txt](https://depot.dev/llms.txt). Append `.md` to any documentation, blog, changelog, or customer URL to fetch its markdown source directly.