Ma77Ball opened a new pull request, #6948: URL: https://github.com/apache/texera/pull/6948
## What Stop pushing docs into the website repo; let the website **pull** them from the release branches instead. - Remove `sync-docs-to-site.yml` (the push sync). - Add a `notify-website` job to `create-release-candidate.yml` that fires a `repository_dispatch` at `apache/incubator-texera-site` after an RC uploads. ## Why `sync-docs-to-site.yml` has failed on **every** run - its `SITE_SYNC_TOKEN` identity (`aicam`) has no write access to `apache/incubator-texera-site`, so the push always 403s. That is why the published docs drifted from the repo (stale JDK/Angular/org references, etc.). The companion site PR ([apache/incubator-texera-site]) makes the website pull `docs/` from the `release/vX.Y` branches at build time, so nothing is committed cross-repo and the site cannot drift. This repo only needs to tell the site to rebuild when a release candidate is cut. ## Notes - The dispatch uses `AUTO_MERGE_TOKEN`. A `repository_dispatch` needs `Contents:write` on the target repo, so that PAT's fine-grained scope must include `apache/incubator-texera-site`; if it does not yet, add the repo to it. The step is `continue-on-error` and the site also rebuilds on a daily schedule, so a missing/underscoped token never blocks releases or doc updates. - Pairs with the site PR; merge order does not matter (the site's schedule covers the gap until both land). 🤖 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]
