Workflow Overview
Core Workflows
Check Version
Automatically detects upstream version updates and creates pull requests
Build Image
Builds and pushes Docker images to multiple registries
Build Test
Local testing workflow for ACT environment
Deploy Pages
Builds and deploys documentation to GitHub Pages
Sync README
Syncs README files to Docker Hub repositories
Workflow Triggers
Check Version Workflow
Runs every 2 hours:
0 */2 * * *Manual trigger with customizable options:
- context: Select specific app or
allapps - create_pr: Whether to create PR (
true,false, ordevelopment) - debug: Enable debug mode
Triggers on push to
master branch when:apps/*/meta.jsonchangesapps/*/Dockerfileorapps/*/Dockerfile.*changesbase/*/meta.jsonor Dockerfile changestest/*/meta.jsonor Dockerfile changes
Add
[skip check] to your commit message to skip the version check workflowBuild Image Workflow
Manual trigger with options:
- context: Required app context (e.g.,
apps/icones) - variants: Build variants (default:
latest) - debug: Debug mode toggle
Triggers on pull requests to
master branchDeploy Pages Workflow
docs/** are modified or manually triggered.
Sync README Workflow
Workflow Jobs
Check Version Jobs
Build Image Jobs
Permissions
Check Version
Build Image
Deploy Pages
Environment Variables
All workflows use the following timezone setting:Registry Credentials
Workflow Outputs
Metadata Job Output
The metadata resolution job outputs a matrix for parallel builds:- Build context and Dockerfile path
- Platform architectures
- Image tags and labels
- Registry push flags
- Pre/post build scripts
Concurrency Control
Deploy Pages
Notifications
The build workflow sends Telegram notifications on successful builds:Next Steps
Version Checks
Learn how automatic version checking works
Image Building
Understand the Docker image build process