CM-53811: unified commit range parse #353
Merged
+73
−23
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
gotbadger
requested review from
elsapet and
mateusz-sterczewski
as code owners
elsapet
approved these changes
Oct 10, 2025
mateusz-sterczewski
approved these changes
Oct 10, 2025
gotbadger
deleted the
CM-53811-fix-commit-range-documents-in-cli-for-sca
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
parse_commit_range_scahad some issues in how it parsed ranges - migrated to use sast version and added more test coverage to verify behaviours are as expected.Fixed flakey test with default branch name
@as1605 This should solve the issues you mentoned here #314 (comment)