add a new flag to exclude subtrees in publish-docs - #145
Merged
rapids-bot[bot] merged 2 commits intoSep 11, 2026
Conversation
jayavenkatesh19
added
improvement
Contributor
|
/merge |
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
2 participants
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.
Add an optional
target-s3-excludeinput to thepublish-docsactionNewline separated glob patterns can be passed to the
aws s3 syncas--excludeflags. These paths are neither uploaded or deleted as a result and a subtree published by another workflow can be independent under the same location.Towards rapidsai/docs#827, with the aim of publishing the deployment docs separate from the main RAPIDS docs.