Ci Workflows

CI Workflow Standards

When to Use This Skill

Version: 2025.1

Standard GitHub Actions workflows for CI/CD automation.

Display name convention

Every workflow's name: follows <Domain>: <Action> [<target>] so the GitHub Actions sidebar groups related workflows alphabetically. Quote the value because YAML treats : inside an unquoted scalar as a key separator. See .claude/rules/workflow-naming.md for the canonical rule, the active domain list, and the cross-workflow rename procedure. Mirror the pattern in any workflow you scaffold here.

Required Workflows

Full YAML, key features, and prerequisites for each file live in references/workflow-templates.md — read it when citing, diffing against, or scaffolding a specific workflow.

2. Release Please Workflow

File: .github/workflows/release-please.yml

See configure-release-please (its REFERENCE.md carries the standard workflow, token, and config templates) for details.

Workflow Standards

Action Versions

Permissions

Minimal permissions required:

permissions:
  contents: read      # Default for most jobs
  packages: write     # For container push to GHCR
  pull-requests: write  # For release-please PR creation

Triggers

Standard trigger patterns:

# Build on push and PR to main
on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

# Also build on release
on:
  release:
    types: [published]

Build Caching

Use GitHub Actions cache for Docker layers:

cache-from: type=gha
cache-to: type=gha,mode=max

Multi-Platform Builds

Build for both amd64 and arm64:

platforms: linux/amd64,linux/arm64

Compliance Requirements

Required Workflows

Required Elements

Status Levels

Secrets Required

Troubleshooting

Build failures, multi-platform issues, and cache misses: see references/troubleshooting.md when a compliant workflow still fails at runtime.