You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Failures in the docs preview cleanup workflow are not analyzed by PR Actions Detective, so maintainers miss automated failure triage/comments for those PRs.
Execute it from the repo root with python /tmp/gh-aw/agent/repro_pr_actions_detective_workflow_name.py.
Expected vs Actual
Expected: Every workflow name listed in on.workflow_run.workflows exists in .github/workflows/*name: fields, so failures from that workflow can trigger PR Actions Detective.
Actual:docs-cleanup is listed as a trigger, but no workflow with name: docs-cleanup exists; the actual workflow is name: docs-preview-cleanup.
See the reproduction script above. It fails deterministically with exit code 1 because docs-cleanup is not a defined workflow name.
Evidence
.github/workflows/trigger-pr-actions-detective.yml:10 includes "docs-cleanup" in workflow_run.workflows.
.github/workflows/docs-preview-cleanup.yml:1 defines the workflow as name: docs-preview-cleanup.
Because workflow_run.workflows must match workflow name exactly, docs preview cleanup failures cannot trigger this detective workflow.
Note
🔒 Integrity filtering filtered 5 items
Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
issue:#unknown (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#16666 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#18134 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#15472 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#17562 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
Impact
Failures in the docs preview cleanup workflow are not analyzed by PR Actions Detective, so maintainers miss automated failure triage/comments for those PRs.
Reproduction Steps
python /tmp/gh-aw/agent/repro_pr_actions_detective_workflow_name.py.Expected vs Actual
Expected: Every workflow name listed in
on.workflow_run.workflowsexists in.github/workflows/*name:fields, so failures from that workflow can trigger PR Actions Detective.Actual:
docs-cleanupis listed as a trigger, but no workflow withname: docs-cleanupexists; the actual workflow isname: docs-preview-cleanup.Script output:
Failing Test
See the reproduction script above. It fails deterministically with exit code
1becausedocs-cleanupis not a defined workflow name.Evidence
.github/workflows/trigger-pr-actions-detective.yml:10includes"docs-cleanup"inworkflow_run.workflows..github/workflows/docs-preview-cleanup.yml:1defines the workflow asname: docs-preview-cleanup.workflow_run.workflowsmust match workflownameexactly, docs preview cleanup failures cannot trigger this detective workflow.Note
🔒 Integrity filtering filtered 5 items
Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)What is this? | From workflow: Bug Hunter
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.