Several of our pipelines commit back to their respective repo after they have finished running a build and executing tests. The initial commit to the repo from a PR successfully reports a passed status in Github, but the commit back with
[skip ci] in the commit message ends up blocking the PR because the status check is required to pass, but Buildkite’s API does not appear to return anything on the webhook call to the API.
In Circle CI, when you use
[skip ci], the build is successfully skipped, and Circle returns a ‘neutral’ status for the required status check, which Github then interprets as a pass, allowing the PR to be merged if all merge constraints are met.
This behavior puts us in a situation where we can’t require specific status checks because they block our PRs indefinitely. I sent an email to support@ and messaged in Slack, but my experience with both of those avenues for support has been lacking.
I’ve included a screenshot of the behavior I’m describing.