-
Notifications
You must be signed in to change notification settings - Fork 28
feat: run incremental scans #302
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
Merged
cx-rui-oliveira
merged 8 commits into
master
from
AST-93068-backend-2-ms-run-incremental-scans-when-last-scanned-commit-is-an-ancestor
Jul 4, 2025
Merged
feat: run incremental scans #302
cx-rui-oliveira
merged 8 commits into
master
from
AST-93068-backend-2-ms-run-incremental-scans-when-last-scanned-commit-is-an-ancestor
Jul 4, 2025
Conversation
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
|
Great job, no security vulnerabilities found in this Pull Request |
…ns-when-last-scanned-commit-is-an-ancestor
…ns-when-last-scanned-commit-is-an-ancestor
cx-julio-silva
approved these changes
Jul 4, 2025
cx-rogerio-dalot
pushed a commit
that referenced
this pull request
Sep 11, 2025
**Proposed Changes** This PR adds a new `--base-commit` flag to the Git plugin that allows users to scan only commits between a specified base commit and HEAD. **Key changes:** - Added `--base-commit` string flag to the Git plugin command - Modified `buildScanOptions()` method to use Git range syntax (`BASE_COMMIT..HEAD`) when base commit is specified - Base commit takes precedence over the `--depth` flag when both are provided - Updated README.md documentation to include the new flag **Use case example:** ```bash # Scan commits between a specific commit and HEAD 2ms git /path/to/repo --base-commit abc123 ``` This implements the Git log functionality equivalent to `git log BASE_COMMIT..HEAD -p -U0`. **Checklist** - [x] I covered my changes with tests. - [x] I Updated the documentation that is affected by my changes: - [x] Change in the CLI arguments - [ ] Change in the configuration file I submit this contribution under the Apache-2.0 license.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.








Proposed Changes
This PR adds a new
--base-commitflag to the Git plugin that allows users to scan only commits between a specified base commit and HEAD.Key changes:
--base-commitstring flag to the Git plugin commandbuildScanOptions()method to use Git range syntax (BASE_COMMIT..HEAD) when base commit is specified--depthflag when both are providedUse case example:
# Scan commits between a specific commit and HEAD 2ms git /path/to/repo --base-commit abc123This implements the Git log functionality equivalent to
git log BASE_COMMIT..HEAD -p -U0.Checklist
I submit this contribution under the Apache-2.0 license.