Skip to content

[ML] Publish overall PR-builds commit status via catalog-info (fix stuck merges) #3129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
edsavage merged 1 commit into from
Jul 28, 2026
+8 −2
Merged

[ML] Publish overall PR-builds commit status via catalog-info (fix stuck merges) #3129

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions catalog-info.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,14 @@ spec:
filter_condition: build.creator.name == 'elasticmachine'
filter_enabled: true
publish_blocked_as_pending: true
publish_commit_status: false
publish_commit_status_per_step: true
# Publish a single overall commit status (buildkite/ml-cpp-pr-builds) rather than
# one per step. This rollup is the required status check on main and the release
# branches, and is what auto-merge (incl. backport auto-merge) waits on. Must stay
# true — if it flips to false the required check never posts and every PR/backport
# blocks forever. (Do not re-enable per-step statuses: they flood the PR and are
# not the required check.)
publish_commit_status: true
publish_commit_status_per_step: false
trigger_mode: code
repository: elastic/ml-cpp
skip_intermediate_builds: true
Expand Down
Loading