NewDeploymentUpdated Aug 30, 20265 min read

GitHub Actions builds and publishes the bot image

The repository workflow keeps container packaging repeatable: pull requests verify that the image can build, while main and version tags publish it to GitHub Container Registry.

01

Workflow triggers

  • Pull requests targeting main build the image without publishing it.
  • Pushes to main publish the latest channel.
  • Version tags matching vX.Y.Z publish semantic version tags and a commit SHA tag.
02

Published image

The image is published as ghcr.io/nateshonor/missionchiefbot-x. Pull the appropriate channel or version tag, then provide credentials only at runtime.

03

What CI checks

BuildKit caching is enabled to shorten repeat builds. The Dockerfile itself remains the source of truth for the Playwright base image, dependencies, sanitized config, and container command.

Was this guide useful?Tell us what could be clearer