DanielLeens opened a new pull request, #11182:
URL: https://github.com/apache/seatunnel/pull/11182
## What does this PR do?
Fix the shared `Build website` CI failure that appears on recent PRs
unrelated to website logic.
The failing website build job currently passes `${{ secrets.GITHUB_TOKEN }}`
into the `seatunnel-website` prebuild step. On contributor fork runs this value
is empty, and `tools/generate-team-pr-contributors.js` exits with:
`GitHub token not found. Set GITHUB_TOKEN/GH_TOKEN or run gh auth login
first.`
This change switches the workflow env wiring to `${{ github.token }}`, which
is the token GitHub Actions provides for the running workflow context.
## Why is this change needed?
`seatunnel-website/tools/generate-team-pr-contributors.js` only reads
`GITHUB_TOKEN` or `GH_TOKEN` before trying `gh auth token`. When the workflow
passes an empty env value, the website build fails before the real docusaurus
build starts.
## Verification
- `./mvnw spotless:apply -nsu -Dmaven.gitcommitid.skip=true -Dskip.ui=true
-T 3C`
- Inspected
`apache/seatunnel-website/tools/generate-team-pr-contributors.js` to confirm
the script reads only `GITHUB_TOKEN` / `GH_TOKEN` and throws the same error
from the failing CI log when neither is present.
## Notes
- This change only updates CI workflow env wiring.
- `seatunnel-engine-ui` was not changed, but this root `spotless:apply`
reactor still executed that module.
- No full local website build was rerun in this repo because the actual
failing code path lives in the GitHub Actions workflow plus the external
`apache/seatunnel-website` checkout.
--
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]
