vinishjail97 opened a new pull request, #848: URL: https://github.com/apache/incubator-xtable/pull/848
## What Makes CI green a hard requirement to merge. `.asf.yaml` branch protection is read **only from the default branch (`main`)** and previously declared no `required_status_checks`, so passing builds were informational, not gating — and `branch-0.4` had no protection at all. Required checks added: - **`main`:** `Maven CI Build`, `License Check` - **`branch-0.4`:** `Maven CI Build`, `License Check`, `validate-spark-runtime-bundle (3.4.3)`, `validate-spark-runtime-bundle (3.5.9)` (The Spark checks are `branch-0.4`-only — there is no spark-runtime module on `main`.) ## Job rename `Maven CI Build` and `License Check` both used a job named `build`, so both reported the **same** status context `build` and couldn't be required distinctly. Each now sets a unique job `name`, giving contexts `Maven CI Build` and `License Check`. A companion PR applies the same rename on `branch-0.4` so those contexts exist there too. ## Merge order Merge **after #843 lands on `branch-0.4`** (it adds the `spark-runtime-validation` workflow and its matrix). INFRA applies `.asf.yaml` wholesale on merge here, so if these rules land first, new `branch-0.4` PRs would block on Spark contexts that aren't running yet. Also merge the `branch-0.4` job-rename PR before/with this so the `Maven CI Build` / `License Check` contexts are produced there. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
