Problem

I see a higher number of QRs in the Chrome Extension than the amount of modified/added code of my Pull Request. Few of the QRs are even in files not modified in my specific PR !

Cause #1 (Most common)

The target branch contains commits that were not merged from the target branch to the pull request branch

Solution #1

Configure the pull request flow to merge from the target branch (even if done locally) prior to running the build scanner

//retrieve the PR source code from the Git based SCM
git clone git@github.repo/repo.git
//retrieve the sha1 before the local merge
export commitSha1 = `git rev-parse HEAD`
//Merge latest changes from the target branch
git checkout branch_name

Cause #2

The target branch contains commits that were not reported to sealights and the user merged from the target branch to the pull request branch

Solution #2

Validate in the CI server (Jenkins, Bamboo…) that the last commit from the SCM (target branch) was reported to Sealights via a build.
If not, initiate a build from both the target branch and then the PR branch.