docker/build-push-action

GitHub Action to build and push Docker images with Buildx

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 12th, 2026
Created on February 17th, 2020
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 735
Total Stargazers: 5,398 (+0)
Total Subscribers: 42 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.4 hours
Mean response time: 16.0 days
90th percentile: 28.8 days
Tracked items: 167

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 8% of issues opened in the past year have been closed. Three people close 73% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 1
Closed in 7 days: 4
Avg open age: 1,062 days
Stale 30+ days: 14
Stale 90+ days: 12

Recent activity

Opened in 7 days: 1
Closed in 7 days: 4
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • status/triage (51)
  • kind/enhancement (20)
  • status/needs-more-info (16)
  • area/cache (11)
  • area/qemu (8)
  • kind/bug (8)
  • kind/upstream (8)
  • registry/github (6)

Detailed Description

docker/build-push-action is a GitHub Action that builds and pushes Docker images using Buildx with full support for Moby BuildKit features.

The action solves the problem of integrating Docker image building into GitHub workflows by wrapping Buildx and BuildKit capabilities. It enables multi-platform builds, secrets management, remote caching, and flexible builder deployment options. By default, it uses Git context to build directly from repository references without requiring a separate checkout step, though it also supports path-based context for cases where files need preprocessing before the build.

Teams should adopt this action when they need to build and push Docker images as part of GitHub Actions workflows, particularly if they require multi-platform support or advanced BuildKit features like remote caching and secrets. The action works well for projects that want to avoid the overhead of checking out the full repository when building from Git is sufficient. The README recommends pairing it with complementary actions: setup-buildx for creating and booting a builder with multi-platform capabilities, setup-qemu for emulation support across additional platforms, and login for Docker registry authentication. The action's Git context approach has a tradeoff: file mutations in preceding workflow steps are ignored since the build operates on the Git reference rather than the working directory, but this can be circumvented by switching to path context with an explicit checkout step.

The project maintains active engagement with its issue tracker and accepts pull requests for bug fixes and feature additions. Development follows a structured approach with clear documentation of inputs, outputs, and environment variables. The codebase is written in TypeScript and published on the GitHub Actions Marketplace for direct integration into workflows.