Ma77Ball opened a new pull request, #7659: URL: https://github.com/apache/texera/pull/7659
### What changes were proposed in this PR? Aligns this repo's CI with the website's new build-time docs sync (merged in apache/incubator-texera-site#72), which pulls each release's `docs/` folder straight from this repo's `release/vX.Y` branches while building the Hugo site. - **Remove `sync-docs-to-site.yml`.** It pushed committed copies of `docs/` into `apache/incubator-texera-site` (`content/docs/latest/`) on every push to `main`. The site no longer stores docs in-tree, so this push-based sync is obsolete and would fight the build-time pull. - **Add `notify-site-rebuild.yml`.** When docs change on a `release/v*` branch, it dispatches the site's existing "Build & Publish Hugo site" workflow (`publish-site.yml`) on `staging` via `workflow_dispatch`, so the edit becomes visible without waiting for an unrelated site commit. The ping is best-effort (`continue-on-error`) and never fails this repo's CI. ### Why not the earlier approach (#6948)? #6948 was written for an earlier site design that added a `repository_dispatch: docs-updated` trigger to the site workflow. The design that actually shipped (#72) does **not** listen for `repository_dispatch`; it exposes `workflow_dispatch`. This PR targets what shipped, and needs no change on the site side. #6948 can be closed in favor of this. ### Configuration required Add a repository secret `SITE_DISPATCH_TOKEN` with **Actions: write** on `apache/incubator-texera-site` (a fine-grained PAT scoped to that repo, or a classic PAT with the `workflow` scope). The old `SITE_SYNC_TOKEN` (Contents: write) used by the removed workflow can be retired. ### Notes / follow-ups - Targets `staging` because #72 currently lives on the site's `staging` branch. Once #72 reaches the site's `main`, add a second dispatch on `--ref main` (production). - The site's `scripts/sync-docs.sh` has an explicit `VERSIONS` list (`release/v1.1`, `release/v1.2`); a brand-new `release/vX.Y` still needs to be added there before it publishes. ### Was this PR authored or co-authored using generative AI tooling? Co-authored with Claude Opus 4.8 in compliance with ASF policy. -- 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]
