Summary
Introduce GitHub Agentic Workflows (gh-aw) to Azure/git-ape to automate repetitive maintainer tasks, keep documentation evergreen, and improve contributor experience — aligning with the repo's mission as a platform engineering framework for the agentic age.
Agentic workflows are authored in Markdown, compiled to hardened GitHub Actions via the gh aw CLI, and run with guardrails (sandboxed execution, scoped tokens, audit trails, output validation). They support multiple engines (Copilot, Claude, Codex).
Motivation
- Reduce maintainer toil on triage, review, and docs upkeep.
- Dogfood agentic patterns in a repo explicitly about the agentic age.
- Provide a reference implementation contributors can learn from.
Proposed workflows
🗂️ Issue management
🔀 Pull Request management
📚 Documentation evergreen
🛠️ Repo maintenance
Implementation plan
- Bootstrap
- Install
gh aw CLI locally for authoring/compiling.
- Add
.github/workflows/agentic/ directory for Markdown workflow sources.
- Document local authoring flow in
CONTRIBUTING.md.
- Guardrails & secrets
- Decide on engine(s): Copilot by default; allow opt-in to Claude/Codex.
- Configure least-privilege
GITHUB_TOKEN scopes per workflow.
- Enable required-reviewer gates on any agent-opened PRs.
- Rollout (phased)
- Phase 1: Issue Triage + PR Describer (low-risk, read/label focused).
- Phase 2: PR Review Agent + Docs Drift Detector.
- Phase 3: CI Failure Triager, Stale Groomer, Health Report, README Refresh.
- Observability
- Enable workflow run summaries and agent audit logs.
- Track metrics: time-to-triage, PR review latency, doc drift PRs merged.
Acceptance criteria
References
Labels (suggested)
enhancement, automation, documentation, good first issue (for individual sub-tasks if broken out)
Summary
Introduce GitHub Agentic Workflows (
gh-aw) toAzure/git-apeto automate repetitive maintainer tasks, keep documentation evergreen, and improve contributor experience — aligning with the repo's mission as a platform engineering framework for the agentic age.Agentic workflows are authored in Markdown, compiled to hardened GitHub Actions via the
gh awCLI, and run with guardrails (sandboxed execution, scoped tokens, audit trails, output validation). They support multiple engines (Copilot, Claude, Codex).Motivation
Proposed workflows
🗂️ Issue management
issues.opened/reopened: classify, apply labels (bug,feature,docs,question), detect likely duplicates, request missing repro info, and post a welcome/next-steps comment.🔀 Pull Request management
pull_request.opened/synchronize: AI-assisted review tuned for Shell best practices (shellcheck-style issues, quoting,set -euo pipefail, error handling, portability).📚 Documentation evergreen
main: detect when script behavior, CLI flags, or configuration diverge fromREADME.md/ docs and open a PR with proposed updates.🛠️ Repo maintenance
main: analyze logs, identify root cause, open or update a tracking issue with a suggested fix.Implementation plan
gh awCLI locally for authoring/compiling..github/workflows/agentic/directory for Markdown workflow sources.CONTRIBUTING.md.GITHUB_TOKENscopes per workflow.Acceptance criteria
gh awbootstrapped and documented inCONTRIBUTING.md.main.no-agentto skip automation).References
Labels (suggested)
enhancement,automation,documentation,good first issue(for individual sub-tasks if broken out)