zhengruifeng opened a new pull request, #57853:
URL: https://github.com/apache/spark/pull/57853

   ### What changes were proposed in this pull request?
   
   Rename the commit-count job in build_main.yml to check-build and make it 
expose a should-build boolean. The downstream Run job now consumes that boolean 
instead of independently evaluating the commit count.
   
   The decision step also prints the repository, branch, commit SHA, commit 
count, decision, and reason. It publishes the same information as a GitHub job 
summary and notice. For skipped Apache branch-4.x builds, the summary includes 
the next qualifying commit count.
   
   ### Why are the changes needed?
   
   When the cadence check succeeds but the Run job is skipped, GitHub marks the 
overall workflow run green. Previously, the count was redirected only to a job 
output, so the run did not visibly explain that Build was skipped or why.
   
   Producing the decision and its explanation in one job makes the green 
gate-only result explicit and keeps the displayed reason synchronized with the 
boolean used by the Run job.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   Ran git diff --check and bash syntax validation for the decision script. 
Also checked the changed workflow for non-ASCII characters and lines over 100 
characters.
   
   No runtime tests were run because this changes only GitHub Actions 
orchestration and reporting.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: OpenAI Codex (GPT-5)


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to