Nick Dimiduk created YETUS-1261:
-----------------------------------
Summary: Default commit status writes to off under GitHub Actions
Key: YETUS-1261
URL: https://issues.apache.org/jira/browse/YETUS-1261
Project: Yetus
Issue Type: Task
Components: Precommit
Reporter: Nick Dimiduk
When --github-token is provided, Yetus unconditionally writes per-subsystem
commit statuses via the GitHub Commit Status API. Under GitHub Actions with
fork PRs, the token lacks statuses: write permission, producing repeated
non-fatal errors:
{noformat}
ERROR: Failed to write github status. Token expired or missing repo:status
write?
{noformat}
The plugin already auto-disables Check Run API calls under GHA because GHA
provides that natively. Commit status writes should follow the same pattern:
default off when ROBOTTYPE == 'githubactions', since the token usually can't
write them anyway.
Add a --github-status-write=<bool> flag (analogous to --github-write-comment
from YETUS-1102). Default true for Jenkins/other CI, default false under GHA.
Callers with sufficient token permissions can opt back in explicitly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
