GitHub integration check only triggered after 2nd CI build

[TomVanBraband]

Hello @JoseLion,

This is due to how CircleCI configures their builds, please see my comment on a similar post.

@TomVanBraband

The scanner reads the environment variables set by CircleCI to either trigger branch or PR analysis. If CircleCI starts a build following a commit on a branch, and there is not yet a pull request open for that branch, then there will not be any environment variables that are related to a pullrequest availablein the build, so we will trigger a regular branch analysis.

When CircleCI starts a build following a commit on a branch for which there is a pull request open, the relevant environment variables are detected and a pullrequest analysis is triggered.