Skip to content

Conversation

@MarshalX
Copy link
Contributor

@MarshalX MarshalX commented May 28, 2025

Notes:

  • Adds compression manifest support for commit range scans
  • Nice to have refactoring (code_scanner.py finally is easy to read)
  • Fixes pre-receive for SCA
  • Updates README

elsapet
elsapet previously approved these changes May 29, 2025
Co-authored-by: elsapet <[email protected]>
@MarshalX MarshalX marked this pull request as ready for review June 10, 2025 15:17
@MarshalX MarshalX requested a review from elsapet June 10, 2025 15:18
@MarshalX MarshalX merged commit 76b8bb3 into main Jun 10, 2025
25 checks passed
@MarshalX MarshalX deleted the CM-48559-commit-range-scans-for-sast branch June 10, 2025 15:23
return git_head_documents, pre_committed_documents, diff_documents


def parse_commit_range_sca(commit_range: str, path: str) -> tuple[Optional[str], Optional[str]]:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MarshalX can we have a proper fix for this now?
The logic breaks especially when the A in A..B is a merge commit.

Using the logic implemented in SAST should be correct

My use-case is running SCA scan from CLI on a Merge Request, so A is the branch point and B is the head of the feature branch. Most of the commits in A are merge commits especially if rebased to latest

Please let me know if you require any contribution for fixing this issue or testing other usecases

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@as1605 hi! Today is my last day at Cycode. I will let my colleagues know about your message. Thank you!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @as1605.
We have noted the issue and we will work on it in the foreseeable future.
We will attempt to use the logic from SAST for SCA scans here, but we need to test it thoroughly to maintain backwards compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants