Ma77Ball opened a new pull request, #68: URL: https://github.com/apache/incubator-texera-site/pull/68
## What Pull docs from `apache/texera` **release branches** at Hugo build time instead of storing a committed copy. - `scripts/pull-release-docs.sh` - enumerate `release/vX.Y` branches; the highest one carrying docs becomes **latest** (`content/docs/latest`, canonical `/docs/...` URLs); older releases are archived under `content/docs/v<maj>-<min>/`. - `scripts/sync-docs.py` - mirror a docs tree into a Hugo content dir, injecting the pre-versioning `/docs/<page>/` alias for **latest only**. - `publish-site.yml` - run the pull before the build; add `repository_dispatch` (fired by texera's release CI) and a daily `schedule` safety net. - Delete the committed `content/docs/latest/` tree; gitignore the generated dirs. `content/docs/_index.md` (the `/docs` → `/docs/latest` redirect) is kept. ## Why `content/docs/` was a committed copy pushed from `apache/texera`. That push sync has been failing (the pushing token lacks write access here), so the copy drifted out of date. Pulling at build time makes drift structurally impossible. ## Behavior today Only `release/v1.2` carries `docs/` (the docs were moved into the repo after `release/v1.1` was cut), so it publishes as **latest** and no archived versions appear yet. When `release/v1.3` is branched, v1.2 automatically moves to `/docs/v1-2/` and v1.3 becomes latest - no workflow change needed. Verified locally against the live release branches: the generated `latest/` reproduces the current site (219 pages identical, 0 front-matter diffs) except 9 pages that update to the newer release-branch content, and one obsolete orphan page (`micro-services-local-dev.md`, not present on `release/v1.2`) drops out. ## Pairs with `apache/texera` PR that removes the broken push sync and adds the release-CI dispatch. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
