blueos-community/Deploy BlueOS Extension

An Action to build and deploy a BlueOS Extension as a docker image.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Mar 11, 2026
License
None

Pinned Snippet

workflow.ymlSHA-pinned
uses: blueos-community/deploy-blueos-extension@aeed6cc216644a168490a184968868e3d626f1ed # v1.5.0

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
docker-usernameYour username for your Docker registry of choice*. Should be stored in a GitHub Action Secret. *Currently only Docker Hub is supported.yes
docker-passwordThe password for your Docker registry authentication. Should be stored in a GitHub Action Secret.yes
github-tokenYour authentification token for GitHub, for uploading image artifacts to a release. Should be set to secrets.GITHUB_TOKEN.yes
build-platformsA comma-separated string of the architectures to build for. Defaults to the ones BlueOS is automatically built for.linux/arm/v7,linux/arm64/v8,linux/amd64
image-nameThe base name for the Docker Images and GitHub Artifacts.yes
image-prefixAn optional prefix for the Docker Image name.blueos-
image-tagAn optional override for the Docker Image tag pushed to the registry. Defaults to the source repository branch or tag name.
authorAuthor Name
author-emailauthor.email@example.com
maintainerThe maintaining organisation or developer.${{ github.repository_owner }}
maintainer-emailmaintainer.email@example.com
contextThe Docker build context directory.no.
dockerfile-locationThe location of the Dockerfile to be used for the build. Defaults to the context directory if not specified.no
skip-checkoutSkip the checkout step (e.g. if files are already present).false

no outputs