This is an automated email from the ASF dual-hosted git repository.

github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion-comet.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new b758f83d76 Publish built docs triggered by 
aae5650cdf5b0ec98c605a3a77d2e9ac66f484fe
b758f83d76 is described below

commit b758f83d764d2a862268e9cffac8fdf14a22497a
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Sep 24 02:40:03 2026 +0000

    Publish built docs triggered by aae5650cdf5b0ec98c605a3a77d2e9ac66f484fe
---
 _images/mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg | 2 +-
 _sources/contributor-guide/ci.md.txt                         | 7 ++++---
 contributor-guide/ci.html                                    | 7 ++++---
 3 files changed, 9 insertions(+), 7 deletions(-)

diff --git a/_images/mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg 
b/_images/mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg
index b506ee1a6b..f602aa696f 100644
--- a/_images/mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg
+++ b/_images/mermaid-013012468fa27c9e9fdb0a14196d357c619c68a8.svg
@@ -1 +1 @@
-<svg id="my-svg" width="100%" xmlns="http://www.w3.org/2000/svg"; 
xmlns:xlink="http://www.w3.org/1999/xlink"; class="flowchart" style="max-width: 
511.73px; background-color: transparent;" viewBox="0 0 511.7299499511719 942" 
role="graphics-document document" 
aria-roledescription="flowchart-v2"><style>#my-svg{font-family:"trebuchet 
ms",verdana,arial,sans-serif;font-size:16px;fill:#333;}@keyframes 
edge-animation-frame{from{stroke-dashoffset:0;}}@keyframes 
dash{to{stroke-dashoffset:0;}}#my-svg [...]
\ No newline at end of file
+<svg id="my-svg" width="100%" xmlns="http://www.w3.org/2000/svg"; 
xmlns:xlink="http://www.w3.org/1999/xlink"; class="flowchart" style="max-width: 
511.73px; background-color: transparent;" viewBox="0 0 511.7299499511719 942" 
role="graphics-document document" 
aria-roledescription="flowchart-v2"><style>#my-svg{font-family:"trebuchet 
ms",verdana,arial,sans-serif;font-size:16px;fill:#333;}@keyframes 
edge-animation-frame{from{stroke-dashoffset:0;}}@keyframes 
dash{to{stroke-dashoffset:0;}}#my-svg [...]
\ No newline at end of file
diff --git a/_sources/contributor-guide/ci.md.txt 
b/_sources/contributor-guide/ci.md.txt
index cea032370e..fa367de798 100644
--- a/_sources/contributor-guide/ci.md.txt
+++ b/_sources/contributor-guide/ci.md.txt
@@ -135,9 +135,10 @@ gh pr edit <number> --add-label run-spark-3.5-tests
 ```
 
 Applying a label starts a new run immediately at the pull request's current 
commit. That run
-executes only the suite the label gates; the PR tier already ran at that 
commit and is not
-repeated. Its aggregate verdict is published as `Required Checks (label run)` 
rather than
-`Required Checks`, so it can be read alongside the commit run without 
replacing it.
+belongs to the separate `Comet CI (label run)` workflow and executes only the 
suite the label
+gates; the PR tier already ran at that commit and is not repeated. Its 
aggregate verdict is
+published as `Label run / Required Checks (label run)` rather than `Required 
Checks`, so it can be
+read alongside the commit run without replacing it.
 
 For a queue-tier suite, that separate name costs nothing: the merge queue runs 
the suite again
 before the change lands, so a failure a label run surfaced still blocks the 
merge later. A
diff --git a/contributor-guide/ci.html b/contributor-guide/ci.html
index 47a1d4fadf..763a73f952 100644
--- a/contributor-guide/ci.html
+++ b/contributor-guide/ci.html
@@ -741,9 +741,10 @@ the only way the suite runs at all.</p>
 </pre></div>
 </div>
 <p>Applying a label starts a new run immediately at the pull request’s current 
commit. That run
-executes only the suite the label gates; the PR tier already ran at that 
commit and is not
-repeated. Its aggregate verdict is published as <code class="docutils literal 
notranslate"><span class="pre">Required</span> <span class="pre">Checks</span> 
<span class="pre">(label</span> <span class="pre">run)</span></code> rather than
-<code class="docutils literal notranslate"><span class="pre">Required</span> 
<span class="pre">Checks</span></code>, so it can be read alongside the commit 
run without replacing it.</p>
+belongs to the separate <code class="docutils literal notranslate"><span 
class="pre">Comet</span> <span class="pre">CI</span> <span 
class="pre">(label</span> <span class="pre">run)</span></code> workflow and 
executes only the suite the label
+gates; the PR tier already ran at that commit and is not repeated. Its 
aggregate verdict is
+published as <code class="docutils literal notranslate"><span 
class="pre">Label</span> <span class="pre">run</span> <span 
class="pre">/</span> <span class="pre">Required</span> <span 
class="pre">Checks</span> <span class="pre">(label</span> <span 
class="pre">run)</span></code> rather than <code class="docutils literal 
notranslate"><span class="pre">Required</span> <span 
class="pre">Checks</span></code>, so it can be
+read alongside the commit run without replacing it.</p>
 <p>For a queue-tier suite, that separate name costs nothing: the merge queue 
runs the suite again
 before the change lands, so a failure a label run surfaced still blocks the 
merge later. A
 nightly-tier suite and Spark 3.4 have no queue run behind them. A red <code 
class="docutils literal notranslate"><span class="pre">Required</span> <span 
class="pre">Checks</span> <span class="pre">(label</span> <span 
class="pre">run)</span></code>


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

Reply via email to