Repository navigation
feat(theme): add the new shared theme, governance docs, and CI to main (2/2) - #1020
Merged
AmilaSamith merged 3 commits intoOct 19, 2026
Merged
Conversation
Step 2 of 2 for promoting the new shared-theme/governance main (built on the fork) to this repo -- see step 1's commit message for the full context. Adds the shared theme (en/src/theme, theme-shared, theme-local, custom.css), the per-branch theme-local extension-point mechanism, governance docs (MAINTENANCE.md, CONTRIBUTING.md, AGENTS.md, HOW_TO_WRITE_A_GUIDE.md, UI_UX_GUIDELINES.md), and the sync/staging/CI workflows (sync-theme.yaml, staging_sync.yaml, promote_to_production.yaml, fork_preview.yaml, broken-link-check.yaml, claude_runner.yml, etc.) that fan this content out to and build each product branch. Co-Authored-By: Claude Sonnet 5 <[email protected]>
AmilaSamith
requested review from
KavinduZoysa,
NipunaRanasinghe,
anupama-pathirage and
rosensilva
as code owners
October 19, 2026 10:27
Contributor
|
Important Review skippedToo many files! This PR contains 172 files, which is 72 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configuration
⛔ Files ignored due to path filters: 61
📒 Files selected for processing: 172
You can disable this status message by setting the 📝 Walkthrough
Comment |
rosensilva
previously approved these changes
Oct 19, 2026
AmilaSamith
dismissed
rosensilva’s stale review
October 19, 2026 10:37
The merge-base changed after approval.
Broken links, images & orphan pages
Links/images come from one crawl of the production build (baseUrl-aware). Orphans are docs not referenced by Summary
Broken links & imagesIntroduced by this PRNo new broken link(s)/image(s) introduced by this PR. ✅ Already on
|
arunans23
approved these changes
Oct 19, 2026
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
3 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.
Summary
Step 2 of 2 for migrating
mainto the new shared-theme/governance model -- see PR 1/2 for the removal of the old content this replaces.Adds:
en/src/theme,theme-shared,theme-local,custom.css) -- authored once here, fanned out to every product branch bysync-theme.yaml.theme-local/per-branch extension-point mechanism (RootExtras,sidebarTransform), so a product branch can hook into shared theme internals without hand-editing them (and having the next sync silently revert it).MAINTENANCE.md,CONTRIBUTING.md,AGENTS.md,HOW_TO_WRITE_A_GUIDE.md,UI_UX_GUIDELINES.md.sync-theme.yaml,staging_sync.yaml,promote_to_production.yaml,fork_preview.yaml, plus CI (broken-link-check.yaml,claude_runner.yml, etc.).206 additions, 23 modifications, 4 renames -- 233 files total.
This branch is built on top of PR 1/2's commit, so until that one merges, GitHub will show this PR's diff as the combined change (~4,400 files). Once PR 1/2 merges into
main, this PR's diff automatically narrows down to just these 233 files -- that's expected, not a sign something's wrong. Please merge PR 1/2 first.Why split into two PRs
See PR 1/2 -- the combined change was timing out GitHub's rule evaluation on merge.
🤖 Generated with Claude Code