Repository navigation
Use the reviewed documentation renderer and publisher - #65
Merged
Merged
Conversation
why: Publish the reviewed reference UI through the owning repository with an immutable shared builder and publisher revision. what: - Bind the docs builder and publisher to the reviewed revision
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
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 docs workflow now builds and publishes through libtmux/docs@98c2031, bringing the reviewed API navigation, reference previews, first-paint styling, installation tabs, and native-port integration into this port’s documentation builds. Both shared references use the same immutable revision.
The exact caller files passed the shared input, permission, source-selection, and immutable-artifact contract checks and independent source review. Actionlint passed.
./gradlew :libtmux-mcp:test checkpassed locally.The normal checks on this PR remain required before merge. Production publication and public-page verification are separate release steps.