Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ on:
type: number
required: false
default: 1
issue-title-prefix:
title-prefix:
description: "Title prefix for created issue (e.g. '[resource-not-accessible-by-integration]')"
type: string
required: false
Expand Down Expand Up @@ -81,7 +81,7 @@ safe-outputs:
noop:
create-issue:
max: 1
title-prefix: "${{ inputs.issue-title-prefix }} "
title-prefix: "${{ inputs.title-prefix }} "
close-older-issues: false
expires: 7d
timeout-minutes: 90
Expand Down Expand Up @@ -184,7 +184,7 @@ Use the prescan output to investigate only workflows that already matched `Resou
- **CAN**: Read files, search code, run commands, create one issue.
- **CANNOT**: Push changes or open PRs in this workflow.
- Only investigate workflows listed in `/tmp/gh-aw/agent/resource-not-accessible-findings.tsv`.
- Do not file a duplicate issue if an open `${{ inputs.issue-title-prefix }}` issue already tracks the same workflows and failure pattern.
- Do not file a duplicate issue if an open `${{ inputs.title-prefix }}` issue already tracks the same workflows and failure pattern.

## Permission reference

Expand Down Expand Up @@ -218,7 +218,7 @@ The fix is to add an explicit `permissions:` block at the workflow or job level

- If the findings file has no data rows, call `noop` with:
`No 'Resource not accessible by integration' failures found in the configured look-back window — nothing to report`.
- Check open issues for `${{ inputs.issue-title-prefix }}` in the title and compare workflow paths/evidence.
- Check open issues for `${{ inputs.title-prefix }}` in the title and compare workflow paths/evidence.
- If an existing open issue already tracks the same findings, call `noop` and reference the existing issue number.

## Step 3: Investigate each affected workflow
Expand All @@ -233,7 +233,7 @@ For each workflow in the findings file:

Call `create_issue` exactly once with:

- **Title**: A short descriptive title summarizing the affected workflows (do NOT repeat the issue-title-prefix in the title)
- **Title**: A short descriptive title summarizing the affected workflows (do NOT repeat the title-prefix in the title)
- **Body**:

````
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ See [example.yml](example.yml) for the full workflow file.
| --- | --- | --- | --- |
| `long-term-branches` | Space-separated list of long-term branch names to scan in addition to the default branch (e.g. `'8.x 7.17'`) | No | `""` |
| `look-back-days` | Number of days to look back when scanning failed workflow runs | No | `1` |
| `issue-title-prefix` | Title prefix used for the combined issue and dedup checks | No | `[resource-not-accessible-by-integration]` |
| `title-prefix` | Title prefix used for the combined issue and dedup checks | No | `[resource-not-accessible-by-integration]` |
| `additional-instructions` | Repo-specific instructions appended to the agent prompt | No | `""` |
| `setup-commands` | Shell commands run before the agent starts | No | `""` |
| `allowed-bot-users` | Allowlisted bot actor usernames (comma-separated) | No | `github-actions[bot]` |
Expand Down