Skip to content

--commit-range flag does not appear to have a substantial effect #9

@bellis-ai

Description

@bellis-ai

I'm trying to set up this tool in my CICD pipeline. My workflow is that, from my local machine, I do a full repository scan. Once that's done, I add a pipeline step to my CICD pipeline that does incremental scans supposedly on the new lines of code that I push up.

Problem is, I don't think the incremental scans are restricted to just the new lines of code that I push up. It appears to always scan the entire repo.

See this repo for a minimal reproducible example: https://gitlab.com/bellis3/aws-codeguru-cli-commit-range-test

It appears to scan lines of code even when no new lines of code are present. It also seems to scan amounts of code that aren't even within the range of the commits. I get no error about using "--commit-range" either, leading me to believe that my usage is correct.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions