Actions
Usage
on:
push:
branches: [main]
pull_request:
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up BuildCharts
uses: buildcharts/setup-action@v1
- name: Generate BuildCharts
uses: buildcharts/generate-action@v1
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
- name: Docker build and test
uses: docker/bake-action@v6
with:
files: .buildcharts/docker-bake.hcl
env:
VERSION: ${{ github.ref_name }}
COMMIT: ${{ github.sha }}
- name: BuildCharts summary
uses: buildcharts/summary-action@v1
Enable caching
BuildKit supports cache backends. On GitHub Actions, type=gha is a common choice.
Example using docker/bake-action to set cache options on the generated _common target:
- name: Docker build and test
uses: docker/bake-action@v6
with:
files: .buildcharts/docker-bake.hcl
set: |
_common.cache-from=type=gha,scope=buildcharts
_common.cache-to=type=gha,scope=buildcharts,mode=max
env:
VERSION: ${{ github.ref_name }}
COMMIT: ${{ github.sha }}
Read more about Cache storage backend and the GitHub Actions cache.
Add build summary
The buildcharts/summary-action reads Docker Buildx history, parses the logs, and generates a summary.
- name: Build summary
uses: buildcharts/summary-action@v1
What each action does
Last modified on April 19, 2026