Add some support for incremental sphinx builds #122
Closed
Conversation
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
Cadair
force-pushed
the
file_env_tracking
branch
from
71a72a6 to
c796410
Compare
Author
|
I need to look into this more |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I noticed that if you modify the tags in a file this is not reflected in a build unless you clean the sphinx env first.
This PR is not perfect as if you trigger the creation of a new tag file on an incremental build, I can't see a way of getting sphinx to pick it up. This is because the
env-get-outdatedevent can only add files to the changed set, not add new files that were not already picked up by the builder.This is still at least an incremental 🥁 improvement on the current situation though.