You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An example case is when having doxygen source folder generated in the top-level sphinx source directory. In that case the users puts in the doxygen folder in exclude_patterns. By default this is not in the autobuild ignore, so it will just loop as the doxygen-sphinx builder constantly re-generates the doxygen source.
Proposal
Add the exclude_patterns from sphinx by default in the autobuild ignore (expanding with the conf.py path). The files there are never meant to be source files that sphinx uses, so it should be safe.
Having this as a default would make the doxygen configuration portable under the vcs, so the user wouldn't have to guess what flags to use for autobuild
Tasks and updates
No response
The text was updated successfully, but these errors were encountered:
Hello. I use sphinx-autoapi, Unfortunately when I activate autoapi_keep_files for faster builds, files are stored in the source directory and sphinx-autobuild detects new files after each build and loops.
Is there a workaround to exclude files to avoid rebuild-loop ? (or should I use the merge request patch ?)
Context
An example case is when having doxygen source folder generated in the top-level sphinx source directory. In that case the users puts in the doxygen folder in
exclude_patterns
. By default this is not in the autobuild ignore, so it will just loop as the doxygen-sphinx builder constantly re-generates the doxygen source.Proposal
Add the
exclude_patterns
from sphinx by default in the autobuild ignore (expanding with the conf.py path). The files there are never meant to be source files that sphinx uses, so it should be safe.Having this as a default would make the doxygen configuration portable under the vcs, so the user wouldn't have to guess what flags to use for autobuild
Tasks and updates
No response
The text was updated successfully, but these errors were encountered: