cloud-fan commented on PR #60098:
URL: https://github.com/apache/spark/pull/60098#issuecomment-6698156829

   Thanks for confirming. I'm fine with this behavior. `build_main.yml` already 
skips its build on every push to a fork's `master` (SPARK-57074), so giving new 
Build checks on fork-master PRs the setup guidance keeps this workflow 
consistent with it. The only cost is the build result on PRs opened from a fork 
`master` last synced before that change, and steering contributors to other 
branches is worth that.
   
   <!-- SPARK_DEV_REVIEW_REPLY 
{"feedback_id":"conversation:6688951787","thread_id":"conversation:6688951787","verdict_sha256":"e3f942cac45ca33f3e1e115d4ab294c6830fd2015f48214d5c290fbe17e4b771"}
 -->


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