

Locally in a gradle managed repository, I create a feature branch:.However, this is what I’m doing that doesn’t look right: So I tested the workflow you posted and I got the same results.
GIT MERGE MASTER INTO BRANCH CODE
Only commits starting from there, up to HEAD are picked up as New Code (NOTE): No merge conflicts expected, no changes to the project we are analyzing are expected either.
GIT MERGE MASTER INTO BRANCH UPDATE
Update the local mainline branch: git checkout master git pull.Create 2 commits, each adding a piece of code.Create a branch from mainline: git checkout -b new_branch.However, this doesn’t work in a merge-workflow. Scanner uses git merge-base HEAD mainline to detect the fork point, all commits starting from that point up to HEAD are considered New Code.

error observed (wrap logs/code around triple quote ``` for proper formatting).
