With that setting, if you push to a branch and then open a PR, if the commit already has a build on that branch then we won’t build again.
If a rebuild is performed (looks to be in this case), it will inherit the environment of the initial build, which will include BUILDKITE_PULL_REQUEST=”false”.
I’d suggest pushing an empty commit to your PR, rather than rebuilding.
The checks appear when your PR triggers a build in Buildkite via webhook. You don’t see any check status for your PR #3 in Github because it didn’t trigger a build. Have you tried creating a new PR from scratch or push an empty commit to your PR to see if that fixes it? I see that you have “Skip when pull request has existing build for commit and branch” turned off now, let us know how you go after trying again.
@faultymajority one more thing I can add here: I notice that you have two GitHub apps configured in your org - ‘GitHub (Limited Access)’ and plain ‘GitHub.’ The ‘GitHub (Limited Access)’ app does not have access to the Extension repo, but the ‘GitHub’ app does. I have a feeling that when commit statuses are posted, we’re hitting the “Limited Access” GH app and silently failing to deliver them because it doesn’t have access to that project/repo in GitHub. I don’t know if there is really a valid use case for having both apps installed in this way. Was that something that you did intentionally?