Skip to content

Fix regression scanner attribution reads #36734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PureWeen merged 1 commit into from
Jul 24, 2026
Merged

Fix regression scanner attribution reads #36734

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 1 addition & 3 deletions .github/workflows/regression-corpus-scanner.lock.yml
View file
Open in desktop

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

6 changes: 5 additions & 1 deletion .github/workflows/regression-corpus-scanner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,9 +139,13 @@ network: defaults
tools:
github:
# The agent only needs the normalized candidate context plus the merged
# introducing PR diff. Filter all fetched content through the integrity proxy.
# introducing PR diff. Keep every agent MCP read integrity-filtered.
toolsets: [pull_requests, repos]
min-integrity: approved
# The deterministic pre-pass applies its own maintainer-association checks before
# extracting attribution. Let its gh calls read those fields without DIFC redaction;
# this does not disable min-integrity filtering on the agent's MCP reads.
integrity-proxy: false
edit:
# Shell utilities plus `git` for local diff/SHA inspection. The executable
# allowlist cannot restrict Git subcommands; safe-outputs is the write boundary.
Expand Down
Loading