yihua opened a new pull request, #19523:
URL: https://github.com/apache/hudi/pull/19523

   ### Describe the issue this Pull Request addresses
   
   `required_status_checks` on master lists every job of the CI matrix as its 
own context. That coupling has two costs: any change to 
`.github/workflows/bot.yml` has to be mirrored here in the same or a follow-up 
commit, and a context that no longer has a job to report it leaves branch 
protection waiting forever. With GitHub Actions disabled on this repository 
over its runner usage, none of those contexts can report at all, so nothing can 
merge.
   
   This is the `.asf.yaml` half of #19514, split out so the required checks can 
be reset before the matrix trim itself lands.
   
   ### Summary and Changelog
   
   Drops the per-job test contexts from `required_status_checks` and keeps the 
four cheap gates: `validate-source`, `validate-pr`, `validate-pr-title` and 
`validate-commit-coauthor`. Reviewers gate on the checks the PR shows. A 
comment in place records why the list is short.
   
   #19514 keeps the workflow trim and adds back a single context, 
`validate-ci-baseline`, together with the job that produces it, so the two stay 
in one commit.
   
   ### Impact
   
   No product code changes, and no change to which jobs run. Only the set of 
contexts branch protection blocks on changes: individual test jobs can now be 
red or missing without blocking the merge button, so a reviewer has to read the 
checks rather than trust the button.
   
   ### Risk Level
   
   low
   
   `.asf.yaml` only, and reversible by restoring the list. Verified that the 
file parses and that `required_status_checks.contexts` resolves to exactly the 
four gates.
   
   ### Documentation Update
   
   none
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable
   


-- 
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]

Reply via email to