Repository navigation
docs: Create docs CLI to facilitate different build combinations - #4000
Merged
Merged
Conversation
To allow more combination of arguments without creating too many UV aliases and while keeping them easy to type.
Contributor
Author
|
Again, merging since its internal tooling and tests pass. PR/Issue 4000! 🎉 |
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.
Continuation of #3998. I think the current amount of available build options for the docs becomes more manageable and flexible with a small CLI wrapper like this. Now we can combine different docs options via flags instead of having unique
uv run task ...commands for each combination. I also made it clearer that the most convenient way to develop locally is viaRegarding the implementation, I went with argparse since I didn't want to take on an extra dependency and this is just some internal tooling for relatively self-explanatory options when building the docs. We could have gone with something fancier like cyclopts or typer, but I think this is sufficient for this purpose.