GitHub Actions maintainer¶
Where to start¶
Read the workflow and governance map and the GitHub API reference.
Where the code lives¶
.github/workflows/: active workflow definitionsscripts/ci/: validation, orchestration, telemetry, and remediation helpers.codex/: WEC, policy, CI-pattern, and operational referencesdocs/ci/anddocs/workflows/: human-facing runbooks and design notes
What this role cares about¶
Least-privilege permissions, pinned actions, branch-scoped concurrency, timeouts, offline-safe gates, WEC integrity, and actionable failure output.
Key technologies¶
GitHub Actions, YAML, Python CI helpers, CodeQL, Ruff, mypy, pytest, nox, pre-commit, dependency scanning, and GitHub MCP/API tooling.
Typical workflow¶
- Identify the workflow category and its supporting script in the workflow map.
- Read repository workflow instructions and governance policy.
- Make the smallest workflow or script change.
- Validate YAML and run the focused script tests.
- Preserve the PR Workflow Execution Checklist and inspect resulting checks.
Common gotchas¶
- Similar workflow names may serve different triggers; inspect each
on:block. - Historical workflow reports can be stale; active definitions are under
.github/workflows/. - Never place secrets in workflow text or logs.
- A workflow can be syntactically valid while violating permissions, concurrency, timeout, or WEC policy.