# CI/CD Pipelines Configured for Headroom: Complete GitHub Actions Workflow Guide > Explore the complete GitHub Actions workflow for Headroom's CI/CD pipeline automating Rust builds, Docker publishing, and multi-platform testing. Get started now. - Repository: [Tejas Chopra/headroom](https://github.com/chopratejas/headroom) - Tags: how-to-guide - Published: 2026-06-21 --- **Yes, the Headroom repository includes a comprehensive CI/CD pipeline powered by GitHub Actions, covering automated testing, Rust builds, Docker image publishing, and multi-platform end-to-end testing.** The `chopratejas/headroom` project maintains a robust continuous integration and delivery infrastructure using GitHub Actions workflows defined in the `.github/workflows` directory. These pipelines automate everything from code quality checks to production releases, emphasizing multi-platform support, security scanning, and developer productivity through automated maintenance tasks. ## Core CI/CD Pipeline Entry Point The **[`ci.yml`](https://github.com/chopratejas/headroom/blob/main/ci.yml)** workflow serves as the primary entry point for the Headroom CI/CD pipeline. It triggers on every push to the `main` branch and on all pull request events. This workflow orchestrates grouped jobs for unit testing, linting, and workflow validation, utilizing caching strategies to speed up subsequent runs. All workflows support manual triggering via the `workflow_dispatch` event, enabling developers to run pipelines on demand for hotfixes or release candidates. ## Language-Specific Build and Test Workflows ### Rust Component Validation The **[`rust.yml`](https://github.com/chopratejas/headroom/blob/main/rust.yml)** workflow handles compilation and testing of Rust components. It executes `cargo test` to verify crate integrity and includes **CodeQL** analysis for security vulnerability detection. This ensures that native Rust code meets quality standards before merging. ### Docker Image Build and Registry Push The **[`docker.yml`](https://github.com/chopratejas/headroom/blob/main/docker.yml)** workflow automates containerization by building images and pushing them to the **GitHub Container Registry**. It manages multi-architecture tags and implements release-candidate logic for versioning. The workflow uses `docker buildx` for cross-platform builds. ```bash # Run Docker build locally mirroring the CI pipeline docker buildx create --use docker buildx bake -f docker/docker-compose.native.yml ``` ## Release Automation and Documentation ### Automated Release Pipeline The **[`release.yml`](https://github.com/chopratejas/headroom/blob/main/release.yml)** workflow orchestrates version bumping, changelog generation, and publication of new releases. It coordinates with the Docker workflow to ensure container images are tagged and published alongside binary releases. ### Documentation Publishing The **[`docs.yml`](https://github.com/chopratejas/headroom/blob/main/docs.yml)** workflow renders project documentation using **MkDocs** and publishes static sites to **GitHub Pages**. This keeps technical documentation synchronized with code changes automatically. ## End-to-End Testing Infrastructure Headroom implements comprehensive E2E testing across multiple platforms through dedicated workflows: - **[`init-e2e.yml`](https://github.com/chopratejas/headroom/blob/main/init-e2e.yml)** – Configures platform-specific test environments for Linux, Windows, and macOS - **[`install-native-e2e.yml`](https://github.com/chopratejas/headroom/blob/main/install-native-e2e.yml)** – Installs native dependencies required for end-to-end test execution - **[`wrap-e2e.yml`](https://github.com/chopratejas/headroom/blob/main/wrap-e2e.yml)** – Aggregates test results and generates execution reports These workflows validate the full application stack across operating systems, catching integration issues before they reach production. ## Maintenance and Auxiliary Automation Beyond core CI/CD functionality, the repository includes automation for project hygiene: - **[`stale.yml`](https://github.com/chopratejas/headroom/blob/main/stale.yml)** – Automatically identifies and closes stale issues and pull requests - **[`pr-health.yml`](https://github.com/chopratejas/headroom/blob/main/pr-health.yml)** – Monitors pull request status checks and linting compliance - **[`network-diff-capture.yml`](https://github.com/chopratejas/headroom/blob/main/network-diff-capture.yml)** – Captures network-level differences for debugging - **[`devcontainers.yml`](https://github.com/chopratejas/headroom/blob/main/devcontainers.yml)** – Manages development container lifecycle and updates ## Manual Workflow Execution Developers can trigger any workflow manually using the GitHub API's `workflow_dispatch` feature. This is useful for running specific pipelines outside of standard git events. Trigger the main CI pipeline manually: ```bash curl -X POST \ -H "Accept: application/vnd.github+json" \ -H "Authorization: token " \ https://api.github.com/repos/chopratejas/headroom/actions/workflows/ci.yml/dispatches \ -d '{"ref":"main"}' ``` Trigger end-to-end tests on demand: ```bash curl -X POST \ -H "Accept: application/vnd.github+json" \ -H "Authorization: token " \ https://api.github.com/repos/chopratejas/headroom/actions/workflows/init-e2e.yml/dispatches \ -d '{"ref":"main"}' ``` ## Summary The Headroom repository implements a complete CI/CD ecosystem through GitHub Actions with the following key characteristics: - **Comprehensive coverage**: From Rust compilation in [`.github/workflows/rust.yml`](https://github.com/chopratejas/headroom/blob/main/.github/workflows/rust.yml) to Docker publishing in [`.github/workflows/docker.yml`](https://github.com/chopratejas/headroom/blob/main/.github/workflows/docker.yml) - **Multi-platform testing**: E2E workflows validate functionality across Linux, Windows, and macOS - **Automated releases**: The [`release.yml`](https://github.com/chopratejas/headroom/blob/main/release.yml) workflow handles versioning, changelog generation, and artifact publishing - **Developer experience**: Manual triggering via `workflow_dispatch` and automated maintenance via [`stale.yml`](https://github.com/chopratejas/headroom/blob/main/stale.yml) and [`pr-health.yml`](https://github.com/chopratejas/headroom/blob/main/pr-health.yml) - **Documentation continuity**: MkDocs deployment through [`docs.yml`](https://github.com/chopratejas/headroom/blob/main/docs.yml) ensures docs stay current ## Frequently Asked Questions ### How do I manually trigger Headroom's CI pipeline? You can trigger the pipeline using the GitHub Actions API with a `workflow_dispatch` event. Send a POST request to the repository's workflow endpoint with your personal access token and specify the target branch, typically `main`. ### What platforms does Headroom's E2E testing cover? The E2E testing infrastructure runs on Linux, Windows, and macOS through specialized workflows including [`init-e2e.yml`](https://github.com/chopratejas/headroom/blob/main/init-e2e.yml), [`install-native-e2e.yml`](https://github.com/chopratejas/headroom/blob/main/install-native-e2e.yml), and [`wrap-e2e.yml`](https://github.com/chopratejas/headroom/blob/main/wrap-e2e.yml). These ensure cross-platform compatibility by testing native installations and full application stacks. ### Where are Headroom's Docker images published? According to the [`.github/workflows/docker.yml`](https://github.com/chopratejas/headroom/blob/main/.github/workflows/docker.yml) configuration, Docker images are built and pushed to the **GitHub Container Registry** (GHCR). The workflow handles multi-architecture tags and coordinates with [`release.yml`](https://github.com/chopratejas/headroom/blob/main/release.yml) for versioned releases. ### Does Headroom use automated security scanning? Yes, the [`rust.yml`](https://github.com/chopratejas/headroom/blob/main/rust.yml) workflow includes **CodeQL** analysis, which performs semantic code analysis to detect security vulnerabilities and coding errors in the Rust codebase. This runs automatically alongside the standard `cargo test` execution.