zhangshenghang opened a new pull request, #11192:
URL: https://github.com/apache/seatunnel/pull/11192
### What is the problem?
After PR #11177, the backend reusable workflow injects a GitHub token into
the website build step through:
```yaml
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```
Recent `Build` workflow runs on `dev` and on PR branches that have synced
the latest `dev` can fail before any job is created, with GitHub reporting
`startup_failure`. In that state there are no Maven/test logs and no `Run /
License header` check run for the notifier workflow to link to.
One visible downstream symptom is that `Notify test workflow` also fails
while trying to detect or link the expected Build result. This makes unrelated
PRs, for example small connector fixes, look blocked even though their source
changes did not run or fail tests.
### Why this change?
The website build only needs the token GitHub provides to the current
workflow run. Using the built-in `github.token` context is enough for both
`GITHUB_TOKEN` and `GH_TOKEN`, and avoids depending on the `secrets` context at
this step inside the reusable backend workflow.
This keeps the intent of #11177: provide a GitHub token to the Docusaurus
build when it needs one. It only changes where that token is read from.
### What changed?
In `.github/workflows/backend.yml`, replace:
```yaml
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```
with:
```yaml
GITHUB_TOKEN: ${{ github.token }}
GH_TOKEN: ${{ github.token }}
```
### Validation
- `./mvnw spotless:apply`
- `./mvnw -q -DskipTests verify`
- `git diff --check`
### Notes
This PR is intentionally separate from JDBC/catalog PRs that are currently
blocked by the CI startup failure. Once this fix is merged into `dev`, those PR
branches can be retriggered or synced with `dev` to verify their own changes
normally.
--
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]
