Every run of the Test job's coverage-upload step fails with an HTTP 403: Coverage upload failed: Code quality is not enabled for this repository. Enable code quality in your repository settings. Confirmed pre-existing — the same two annotations already appeared on the 32fc584 main run, before any of this session's changes, so this isn't a regression from a recent merge.
The job itself still passes (the action treats it as an annotation, not a failure), but the annotation is real noise on every run. Two ways to resolve, either is a repo-owner decision rather than a code change:
- Enable GitHub's Code quality feature for this repository (Settings > Code security and analysis), so the coverage upload actually has somewhere to land.
- If coverage-upload isn't wanted, add
fail-on-error: false to the upload step (or drop the step entirely) so it stops annotating every run.
Link: https://docs.github.com/en/code-security/how-tos/maintain-quality-code/set-up-code-coverage
Every run of the
Testjob's coverage-upload step fails with an HTTP 403:Coverage upload failed: Code quality is not enabled for this repository. Enable code quality in your repository settings.Confirmed pre-existing — the same two annotations already appeared on the32fc584main run, before any of this session's changes, so this isn't a regression from a recent merge.The job itself still passes (the action treats it as an annotation, not a failure), but the annotation is real noise on every run. Two ways to resolve, either is a repo-owner decision rather than a code change:
fail-on-error: falseto the upload step (or drop the step entirely) so it stops annotating every run.Link: https://docs.github.com/en/code-security/how-tos/maintain-quality-code/set-up-code-coverage