Repository navigation
Align nine workflow tool allowlists and warn on denied prompt tools #66554
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.
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
Changes from 2 commits
a26f800
6974129
d75287d
64b5fb7
530e7ad
4682a78
299fbbd
c20f9b3
077b9f1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
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 |
|---|---|---|
|
|
@@ -39,7 +39,7 @@ imports: | |
| - shared/graders.md | ||
| tools: | ||
| cli-proxy: true | ||
| bash: ["cat:*", "git diff:*", "git diff --binary --no-ext-diff | wc -c", "git restore:*", "git status:*", grep, "head:*", jq, ls, "sed:*", tail, wc] | ||
| bash: ["cat:*", cut, "git diff:*", "git diff --binary --no-ext-diff | wc -c", "git restore:*", "git status:*", grep, "head:*", jq, ls, "sed:*", tail, wc] | ||
| github: | ||
| mode: local | ||
| github-token: "${{ secrets.GITHUB_TOKEN }}" | ||
|
|
@@ -114,6 +114,8 @@ Your goal is to: | |
|
|
||
| ## Workflow Steps | ||
|
|
||
| Use native edit tools for writing cache records and report bodies rather than shell heredocs. Safe outputs are CLI-mounted: invoke `safeoutputs <tool>` through bash (use `--help` for parameters), not an invented native safe-output tool. | ||
|
|
||
| ### 1. Check Cache for Previously Fixed, Oversized, or Stalled Alerts | ||
|
|
||
| Before selecting an alert, check the cache memory for prior outcomes: | ||
|
|
@@ -131,7 +133,7 @@ Before selecting an alert, check the cache memory for prior outcomes: | |
|
|
||
| ### 2. List All Open Alerts | ||
|
|
||
| Use `list_code_scanning_alerts` to list all open code scanning alerts. | ||
| Run `github list_code_scanning_alerts` through bash to list all open code scanning alerts. The GitHub CLI wrapper is available; do not invent a `github-list_code_scanning_alerts` tool name. | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. All GitHub reads now use the CLI-mounted |
||
| - Sort the results in reverse importance/severity priority (highest first) | ||
| - Use `rule.security_severity_level` when available (`critical > high > medium > low`) | ||
| - Fall back to alert/rule severity when no security severity is present (`error > warning > note`) | ||
|
|
@@ -156,7 +158,7 @@ Immediately after selecting the alert, and **before** doing any analysis or fix | |
|
|
||
| ### 4. Get Alert Details | ||
|
|
||
| Get detailed information about the selected alert using `get_code_scanning_alert`. | ||
| Get detailed information about the selected alert using `github get_code_scanning_alert` through bash. | ||
| - Extract key information: | ||
| - Alert number | ||
| - Severity level (critical, high, medium, low, warning, note, or error) | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All safe-output actions now use the CLI-mounted
safeoutputscommand through bash, includingcreate-pull-request,create-issue, andnoop. Fixed inc20f9b3.