andygrove opened a new pull request, #5863:
URL: https://github.com/apache/datafusion-comet/pull/5863

   ## Which issue does this PR close?
   
   None. Documentation follow-up to #5843.
   
   ## Rationale for this change
   
   #5843 changes what contributors see on their pull requests: the macOS build, 
the benchmark check and the Spark 3.4/3.5/4.0 and Iceberg 1.8/1.9/1.10 suites 
move behind the merge queue, with `run-*` labels to opt a pull request back in. 
The workflows README explains the mechanics for whoever maintains CI, but there 
was nothing in the contributor guide that tells a contributor what runs where, 
which label to apply, or what to do when a queue run fails.
   
   ## What changes are included in this PR?
   
   A new `Continuous Integration` page under Testing in the contributor guide 
covering:
   
   - the PR tier and the queue tier, and why the Linux build is the one test 
job that still runs on push to `main`
   - the opt-in labels, when a change warrants one, and what a label run does 
and does not run
   - how a committer queues a merge and what GitHub does with it
   - how to find a queue failure, how to tell an infrastructure failure from a 
test failure, and how to reproduce a queue failure on the pull request by 
merging `main` and applying the suite's label
   - what to run locally before changing CI
   
   The development guide's test-suite registration section now links to it, and 
no longer names `pr_missing_suites.yml`, which was folded into `preflight` some 
time ago.
   
   ## How are these changes tested?
   
   `prettier --check` on the changed Markdown. The page describes the state of 
CI after #5843 merges, so this PR should land after it. Marked draft until then.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01BtAqq4YJsk8uk42c7vHk8B
   


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