Fix required CI checks stuck on PRs touching openmetadata-service#25937
Merged
Fix required CI checks stuck on PRs touching openmetadata-service#25937
Conversation
Code Review ✅ ApprovedClean CI configuration fix. Removing OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change:
Was this helpful? React with 👍 / 👎 | Gitar |
akash-jain-10
approved these changes
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two branch protection required checks (
maven-postgresql-ciandpy-run-tests (3.11)) were permanently stuck as "Waiting for status to be reported" on PRs modifyingopenmetadata-service/**, blocking merges.The repo uses a skip/run workflow pattern where a "real" workflow runs on relevant path changes and a "skip" workflow reports a passing no-op status otherwise. The gap:
workflow_dispatchonly), but the skip workflow still hadpaths-ignoreexcluding service paths. Neither workflow reported the check. Fix: removepaths-ignoreso the skip workflow always runs.py-version: ['3.10']in its matrix, so it never produced a 3.11 check. The skip workflow (which includes 3.11) was excluded bypaths-ignore. Fix: add'3.11'to the real workflow's matrix.