fix(scan): Skip changed-line budget for explicit file scans#422
Merged
Conversation
Explicit local file-target runs now bypass maxChangedLines because the user already selected the files to scan. PR and diff-based runs still enforce that budget, and the existing file count and file size limits continue to apply. Fixes #419 Co-Authored-By: GPT-5 Codex <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Explicit local file-target scans now ignore
maxChangedLines, so a user-supplied target list is not partially skipped by the PR/diff changed-line safety budget. PR and diff-based scans still enforce that budget, and explicit file-target scans still enforce the existing file count, file size, ignore, generated-file, and chunking limits.The regression coverage exercises explicit file targets bypassing
maxChangedLines, verifiesmaxFilesstill applies, and checks trigger path filtering preserves the explicit-target context marker. The scan config docs now describemaxChangedLinesas a PR/diff scan budget.Fixes #419