Skip to content

deploy-github-actions.md

Latest commit

 

History

History
42 lines (35 loc) · 1.32 KB

deploy-github-actions.md

File metadata and controls

42 lines (35 loc) · 1.32 KB
Raw

Run in GitHub Actions

Use GitHub Actions for issue triage, PR review, test reproduction, and release checks where the repository is already checked out.

This pattern is best for CLI-only agents or agents that use explicit CommandDef/SessionEnv capabilities. Keep GitHub credentials in Actions secrets and pass only the minimum token scope needed by the job.

name: agentic-harness

on:
  issues:
    types: [opened]

jobs:
  triage:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      issues: write
    steps:
      - uses: actions/checkout@v4
      - uses: dtolnay/rust-toolchain@stable
      - run: cargo install --path crates/agentic-harness-cli
      - run: |
          agentic-harness run triage \
            --workspace . \
            --id "issue-${{ github.event.issue.number }}" \
            --payload '{"issueNumber":${{ github.event.issue.number }}}'
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Register gh, git, or package-manager commands only from trusted Rust code with CommandDef or a sandbox SessionEnv; do not put secrets in prompts.

For pull-request workflows, change the trigger and permissions explicitly. For example, PR review jobs usually need contents: read and may need pull-requests: write only if the agent posts comments or opens follow-up changes.