Repository navigation
chore: remove legacy IA/content ahead of shared-theme main migration (1/2) - #1019
Merged
AmilaSamith merged 1 commit intoOct 19, 2026
Merged
Conversation
Step 1 of 2 for promoting the new shared-theme/governance main (built on the fork) to this repo. main no longer carries full product docs content directly -- that now lives on each product branch (saas/wso2-integrator/ wso2-connectors), synced out from a much smaller main that holds only the shared theme, governance docs, and CI. This removes everything that model no longer puts on main, ahead of step 2 (the new content itself), so each PR stays within GitHub's ruleset evaluation limits instead of one combined ~4,400-file change timing out. None of this is live-site content -- gh-pages is built from `staging`, which comes from the product branches via staging_sync.yaml, not from main directly, so main never served any of this in production. 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
WalkthroughWarning Review details and warnings were omitted to fit the comment limit. |
rosensilva
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
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.
Summary
Step 1 of 2 for migrating
mainfrom the old full-docs-tree model to the new shared-theme/governance-only model (see PR 2/2 for the actual new content).en/docs/**(legacy IA, including the fullconnectors/tree -- ~379K of the ~435K deleted lines) and the other content this architecture no longer puts onmain.Why split into two PRs
The combined change (this + PR 2/2) is ~4,400 files and was timing out GitHub's rule evaluation on merge ("The rule did not run because of a timeout"). Splitting by change type (pure delete here, pure add/modify in PR 2/2) keeps each one within whatever limit the rule evaluator is hitting, and is also just a more reviewable diff than one giant mixed change.
Is this safe?
Yes --
mainis not what serves the live site. Production (gh-pages) is built from thestagingbranch, which is populated bystaging_sync.yamlrunning on each product branch (saas/wso2-integrator/wso2-connectors), not frommaindirectly. None of this removed content was live production source by the time this merges.Merge order
This PR should merge before PR 2/2 (which is branched on top of this one).
🤖 Generated with Claude Code