Workflow Templates

Workflow templates are thin caller workflows (~20 lines each) installed in target repositories. Each caller declares its trigger event and permissions, then delegates to the corresponding shared reusable workflow in buck-bronson. The bucky CLI installs the code review workflow.

Installed workflows

Workflow	Trigger	What it does
bucky-code-review.yml	pull_request	AI code review when PRs are opened or updated

How they work

Each caller workflow:

1. Declares trigger events and required permissions
2. Calls the corresponding reusable workflow in buck-bronson with @v1
3. Uses secrets: inherit to forward all repo/org secrets

Example: bucky-code-review.yml

name: Bucky Code Review
on:
  pull_request:
    types: [opened, synchronize, reopened]

permissions:
  contents: read
  pull-requests: write
  id-token: write

jobs:
  review:
    uses: fetch-rewards/buck-bronson/.github/workflows/bucky-code-review.yml@v1
    secrets: inherit

CLI substitutions

When the CLI generates the caller workflow, it rewrites @main refs to @v{major} (e.g., @v1) on lines referencing the buck-bronson repo.

Permissions

The code review caller workflow requests these permissions:

Permission	Level	Purpose
contents	write	Read/write repo files, create branches
pull-requests	write	Create and comment on PRs
id-token	write	OIDC authentication for AWS Bedrock
actions	read	Read workflow run information