Skip to content

feat(templates): ready-to-fork Actions dispatch workflow + guide - #747

Open
matt82198 wants to merge 4 commits into
mainfrom
feat/actions-dispatch-template
Open

matt82198 wants to merge 4 commits into
mainfrom
feat/actions-dispatch-template

Conversation

@matt82198

Copy link
Copy Markdown
Owner

Summary

Ready-to-fork GitHub Actions dispatch template for adopters to integrate aesop orchestration into their CI/CD pipelines.

  • templates/aesop-dispatch-template.yml: comment-documented YAML workflow with workflow_dispatch (manual trigger) + optional cron; configurable environment variables (AESOP_COST_CEILING, AESOP_CONCURRENCY, model tier); includes cost-summary and failure-visibility steps
  • docs/ACTIONS-TEMPLATE.md: comprehensive adopter guide (quick start, environment variables, workflow steps, permissions, examples, troubleshooting)
  • tests/test_actions_template.py: 5-test suite (YAML validity, workflow structure, CLI command existence verification, no invented flags, no fabricated outputs)
  • All CLI commands verified against bin/cli.js --help output per spec (doctor, wave preflight, status, fleet, reproduce, wave scorecard exist and are quoted)

Test Plan

  • Test suite passes: 5/5 tests [PASS]
    • YAML syntax validation
    • Workflow structure integrity (required keys, permissions, steps)
    • CLI command existence (workflow_dispatch options verified against bin/cli.js --help)
    • No invented flags or undocumented options
    • No fabricated command outputs
  • Secret scan: CLEAN (0 violations)
  • Test count gate: regenerated (Python: 237 suites)
  • Committed and pushed (no stash, no --no-verify, no --admin/--auto)

Generated with Claude Code

matt82198 and others added 2 commits August 3, 2026 12:15
Add GitHub Actions dispatch workflow template for adopter CI/CD integration:
- templates/aesop-dispatch-template.yml: comment-documented workflow with
  workflow_dispatch + optional cron; demonstrates aesop CLI invocation
  (doctor, wave preflight, status, reproduce); cost-summary and failure
  visibility steps; customizable AESOP_COST_CEILING + AESOP_CONCURRENCY
- docs/ACTIONS-TEMPLATE.md: adopter guide (setup, customization, examples,
  troubleshooting, FAQ; documents GITHUB_TOKEN caveat per spec)
- tests/test_actions_template.py: comprehensive test suite verifying YAML
  syntax, workflow structure, CLI command existence, no invented flags,
  no fabricated outputs (5-test suite, all CLI commands quoted + verified)
- Updated docs/README.md (one index line in Stage 1)
- Updated tools/CLAUDE.md (new Templates section documenting adopter resources)

All invoked aesop commands (doctor, wave preflight, status, fleet, reproduce,
wave scorecard) verified against bin/cli.js --help ground truth per spec.
Template never executes in this repo (lives in templates/, not .github/workflows/).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@matt82198 matt82198 added the merge-queue Queued for the merge-queue advancer daemon label Aug 3, 2026
matt82198 and others added 2 commits August 3, 2026 14:17
…/CLAUDE.md

#751 replaced the inline per-tool index in tools/CLAUDE.md with the generated
tools/INDEX.md, cutting the file to 33 lines. This branch's addition is NOT an
index line -- it is a real "Templates & Adopter Resources" section -- so the
conflict is resolved by taking main's 33-line file and re-appending that
section verbatim (39 lines total). No content lost on either side.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-queue Queued for the merge-queue advancer daemon

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant