-
Notifications
You must be signed in to change notification settings - Fork 18
fix(#1190): rewrite scanner-blocked shell snippets in skill files #1191
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
Open
fullsend-ai-coder
wants to merge
4
commits into
main
Choose a base branch
from
agent/1190-fix-scanner-blocked-snippets
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+83
−47
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f67432a
fix(#1190): rewrite scanner-blocked shell snippets in skill files
fullsend-ai-coder[bot] bc436be
fix(#1190): convert remaining scanner-blocked bracket tests in code-i…
fullsend-ai-coder[bot] 74c846b
fix: address review feedback on PR #1191
fullsend-ai-coder[bot] 3fc4eaa
fix(#1190): make gitlab-api.curlrc self-contained per consuming block
fullsend-ai-coder[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
[low] secret-exposure
GITLAB_TOKEN is written once at Environment setup to the predictable path /tmp/gitlab-api.curlrc and reused by later, independent fenced blocks (MR metadata/changes at lines 38/46, issue context at 112/118, prior-review compare at 127). The only scrub instruction for this file is prose after the last optional section (lines 132-137), not a fenced bash call and not an in-block truncate. This is weaker than the sibling /tmp/pr-head.curlrc pattern in the same file, which truncates inside its own fenced script (line 99) in addition to a follow-up prose scrub (line 105). If a reviewing agent skips the issue-context or prior-review-compare sections, or stops before the trailing prose instruction runs, /tmp/gitlab-api.curlrc keeps the token at a well-known path for the rest of the sandbox lifetime. Impact is bounded (token already present in the sandbox environment; described as read-only), but this introduces a new persistent on-disk copy the previous --header pattern did not create.
Suggested fix: Make each consuming fenced block self-contained: recreate the curlrc at the start of the block, use it, then truncate it (
: > /tmp/gitlab-api.curlrc) at the end of that same block, matching the /tmp/pr-head.curlrc patterns in-block truncate plus follow-up scrub.