Conversation
Setting autosectionlabel_prefix_document = True prefixes every auto-generated section label with its document path, preventing collisions when multiple notebooks share identical headings like "General Use" or "Feature Names". Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Three root causes resolved: - language_model_game.ipynb was doubly-wrapped: the file contained a single raw cell whose source was the entire notebook JSON. Unwrapped to the correct 31-cell notebook, fixing 129 repeated toc.no_title warnings (nbsphinx fired once per output page because no title was visible). - Deleted orphaned api/shapiq.imputer.conditional_imputer.rst which referenced a module that no longer exists, causing an autodoc import failure and a "document not in toctree" warning. - Added examples/GALLERY_HEADER.rst to exclude_patterns so sphinx- gallery's header file does not produce a "document not in toctree" warning (sphinx-gallery includes it internally via auto_examples/). The docs now build with -W --keep-going without any warnings. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
# Conflicts: # src/shapiq/tree/base.py
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Advueu963
requested changes
Mar 16, 2026
Collaborator
Advueu963
left a comment
There was a problem hiding this comment.
Noice changes! Can we quickly talk about this .md file that exists here. Should it be removed?
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
Signed-off-by: Maximilian <maximilian.muschalik@gmail.com>
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.
Motivation and Context
I wanted to remove all warnings for the docs building process and clean up the existing docstrings to come to a clean slate state in terms of documentation. Adaptions and changes can now be made more easily and should be of a much higher quality. Looking forward to more improvements here. :)
Important: We now have a CI test to break on any docs issues. ❤️
Public API Changes
How Has This Been Tested
Extensively in CI and locally.