Automation patterns

Connect DebugBundle GitHub automation to repository_dispatch workflows, fetch full bundle context in GitHub Actions, and hand off to repository-owned automation.

GitHub automation is available on Solo and Team plans.

repository_dispatch to GitHub Actions

Connect a project repo in the dedicated GitHub project tab, let DebugBundle emit repository_dispatch, and start triage inside GitHub Actions.

Reference action for full context

Use debugbundle/action to fetch the full bundle and reproduction into the canonical .debugbundle/bundles/cloud layout.

Repository-owned automation

After the fetch step, let your workflow decide whether to open an issue, invoke an agent, create a PR, or stop.

DebugBundle's GitHub automation path is intentionally narrow:

Open the project's GitHub tab and connect GitHub.
Assign one primary repository to the project.
Create dispatch rules that select which lifecycle events should trigger automation.
Receive repository_dispatch in GitHub Actions. Incident dispatches can fetch full incident context with debugbundle/action; hosted improvement dispatches include improvement_id plus a bundle link for repository-owned workflows that want to fetch the improvement bundle directly. Incident-backed improvement opportunities do not emit improvement_bundle.created; agents should fetch the related incident bundle instead.

DebugBundle owns the dispatch. Your repository owns the policy after the workflow starts.

Example flow

$ debugbundle github status --project-id proj_123
$ debugbundle github rules --project-id proj_123
$ gh workflow view .github/workflows/debugbundle.yml

The action and workflow examples live alongside the product docs:

examples/github-actions/basic.yml
examples/github-actions/agent-capable.yml
examples/github-actions/issue-creation.yml

The fetch action itself is published separately at debugbundle/action@v1.