Repository navigation
ci(docs) Adopt header menus and reference fixes - #786
Merged
Merged
Conversation
what: - Add GitHub, package and external documentation menus to the site header, each row showing its destination's icon - Show a parameter's type and optional marker against its name, print an overload note as "for <label>" without doubled parentheses, and keep the brackets of [source] links outside the link - Finish page appearance before revealing it, and load pages with ordinary document loads instead of the client router - Upload content-hashed assets before the HTML that names them, keep earlier hashes, and cache them as immutable - Start optional Cloudflare Web Analytics after page load, only where the edge grants permission - Outside Python, present available MCP and workspace companions as concept examples - Wrap Python declarations at the 60-column reference width the way ruff format does - Render a reST rubric with no body as a heading why: The header carried no repository, package or off-site API reference links. Only a port's landing and overview pages listed them together, and every other page offered one footer GitHub link. Shared source: libtmux/docs From: 9f5cef954e3c52e7eb239a3da56a34f92b69f161 To: 7ffc04bceec2cada8149a32e46926cba9fa9ecd2
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## docs-site-deploy #786 +/- ##
====================================================
+ Coverage 52.37% 52.45% +0.08%
====================================================
Files 26 26
Lines 3729 3729
Branches 747 747
====================================================
+ Hits 1953 1956 +3
+ Misses 1472 1469 -3
Partials 304 304 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Pin only the shared port builder and publisher to
7ffc04bceec2cada8149a32e46926cba9fa9ecd2from9f5cef954e3c52e7eb239a3da56a34f92b69f161. All other workflow bytes, library contents, triggers, permissions and language/source/version inputs remain unchanged.Every port page now has header menus for its GitHub repositories, package registries and off-site API references, with the destination's icon on each row; a menu with no entries is hidden. Callable signatures for C#, F#, PowerShell, C++, Swift, Julia, Python, Ruby and Lua now wrap at the 60-column reference width the way each language's formatter or native help lays them out. Pages render complete before they are shown.
The exact required CI and root merge receipts of the shared checkpoint must be verified before this operator runs. This PR does not claim an owner build or publication pass. Root reviews this exact caller diff, actual repository-required checks and reviews before merge; optional native estate checks are not a new universal gate.
Execution route:
exact_source_manual_dispatch_after_root_controlled_pin_merge. Root separately schedules reviewed merges and exact source requests from the actual workflow state. If the current active workflow already publishes the intended source on merge, retain that actual event and do not issue a duplicate request. Future source/native/run identities will be bound to actual events.