github-actions.mdx

Use this when repository checks run in GitHub Actions and agent-generated work should not merge until task state and CI evidence are both legible.

Agentplane does not replace GitHub branch protection. It gives branch protection a repo-local evidence artifact to inspect.

When to use

• Your repository already uses GitHub Actions for required checks.
• You want Agentplane task records to explain why an agent change is ready for review.
• You use pull requests or branch protection.

Handoff prompt

Give this to the coding agent:

Use Agentplane as the task harness and GitHub Actions as the hosted gate. Keep PR artifacts current,
wait for the required checks, record the local and hosted verification result, and stop before merge
if checks are red or scope changed.

Integrate only after the required hosted checks are green and the task evidence matches the diff.

ACR gate shape

For task-bound pull requests, CI can validate the Agent Change Record with a concrete task id:

- run: npm i -g agentplane
- run: agentplane acr check <task-id> --mode ci

For reusable team workflows, wrap task-id discovery in your repository's PR convention or a future first-class Agentplane action.

Expected repo artifacts

• task README with PR metadata;
• .agentplane/tasks/<task-id>/pr/ local PR artifacts;
• verification note referencing local checks and hosted CI result;
• final merge/finish metadata.

Limitations

Agentplane does not replace GitHub branch protection. Use your repository's existing required checks and PR review rules as the hosted gate.