Jenkin 2.138 Branch-Source plugin 2.4.2 SCM=Github Enterprise Amazon Linux Hi,
We've recently started converting from freestyle jobs to Jenkinsfile/pipelines. We're seeing odd behaviors when pull requests(PR) are created directly from our main repo and not from a fork of the repo. Specifically around the git status checks. PRs that are NOT created from a fork result in two git checks and 2 full builds being kicked off. We see these 2 checks: continuous-integration/jenkins/branch continuous-integration/jenkins/pr-merge The PRs from the developers fork, cause only 1 check and 1 build. continuous-integration/jenkins/pr-merge Does anyone know how the 2 checks get created? Whats the difference between continuous-integration/jenkins/branch and continuous-integration/jenkins/pr-merge? Thanks, Tom -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7c18652a-1938-487a-ab70-a1e652010e5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
