[DOC] Fix "document isn't included in any toctree" warnings#7222
Closed
dnskr wants to merge 1 commit intoapache:masterfrom
Closed
[DOC] Fix "document isn't included in any toctree" warnings#7222dnskr wants to merge 1 commit intoapache:masterfrom
dnskr wants to merge 1 commit intoapache:masterfrom
Conversation
Signed-off-by: dnskr <dnskrv88@gmail.com>
2d2ebb4 to
cf7fb1f
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7222 +/- ##
======================================
Coverage 0.00% 0.00%
======================================
Files 696 696
Lines 43530 43530
Branches 5883 5883
======================================
Misses 43530 43530 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
pan3793
approved these changes
Oct 8, 2025
cxzl25
reviewed
Oct 10, 2025
cxzl25
approved these changes
Oct 12, 2025
dnskr
added a commit
that referenced
this pull request
Oct 15, 2025
…nings ### Why are the changes needed? The PR fixes a few `document isn't included in any toctree` issues: * Page `JVM Quake Support` now included into `Extensions for Spark` menu: ```shell ./kyuubi/docs/extensions/engines/spark/jvm-quake.md: WARNING: document isn't included in any toctree ``` * Page `Z-order Benchmark` consolidated with `Z-Ordering Support` page: ```shell ./kyuubi/docs/extensions/engines/spark/z-order-benchmark.md: WARNING: document isn't included in any toctree ``` * File `requirements.txt` added to `exclude_patterns`: ```shell ./kyuubi/docs/requirements.txt: WARNING: document isn't included in any toctree ``` ### How was this patch tested? Checked that there are no warnings mentioned above during the documentation build process. ```shell make html ``` ### Was this patch authored or co-authored using generative AI tooling? No Closes #7222 from dnskr/doc-fix-document-isn't-included-in-any-toctree. Closes #7222 cf7fb1f [dnskr] [DOC] Fix "document isn't included in any toctree" warnings Authored-by: dnskr <dnskrv88@gmail.com> Signed-off-by: dnskr <dnskrv88@gmail.com> (cherry picked from commit 54212ef) Signed-off-by: dnskr <dnskrv88@gmail.com>
Contributor
Author
|
Merged to master(1.11.0) and branch-1.10(1.10.3) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why are the changes needed?
The PR fixes a few
document isn't included in any toctreeissues:Page
JVM Quake Supportnow included intoExtensions for Sparkmenu:./kyuubi/docs/extensions/engines/spark/jvm-quake.md: WARNING: document isn't included in any toctreePage
Z-order Benchmarkconsolidated withZ-Ordering Supportpage:./kyuubi/docs/extensions/engines/spark/z-order-benchmark.md: WARNING: document isn't included in any toctreeFile
requirements.txtadded toexclude_patterns:./kyuubi/docs/requirements.txt: WARNING: document isn't included in any toctreeHow was this patch tested?
Checked that there are no warnings mentioned above during the documentation build process.
Was this patch authored or co-authored using generative AI tooling?
No