docs: clarify Java API selector requirements in pipeline-commands - #79
Merged
WilliamAGH merged 1 commit intoJul 17, 2026
Conversation
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
The doc set filtering section implied all sets accept 'IDs or paths', but
Java API sets only accept the canonical relative mirror path (e.g.,
'java/java21-complete'), not hyphenated ID forms like 'java21-complete'.
Non-Java sets continue to accept both forms.
Example wrong turn: An agent might try '--doc-sets=java21-complete'
(mimicking the non-Java ID pattern 'spring-boot-complete'), which would
fail silently for Java API sets.
Introduced by commit b95c521 (@WilliamAGH, #77)
Doc Drift PRs can be configured here.