Summary
Add CI gating for GitHub-integration tests (tests that require GH auth or network access) and small diagnostics/observability polish for the HealthService logs.
(see parent issue #7687)
Motivation
Integration tests that require gh or a GITHUB_TOKEN should be explicitly gated in CI to avoid flakiness. Separate this operational/CI-level work from the core HealthService bugfix to keep reviews focused.
To do
- Add CI/test harness support to skip GitHub-integration tests unless a flag like
RUN_GH_INTEGRATION=true is set in the environment.
- Update test code to respect the gate (skip or mark tests as skipped when token/gh missing).
- Optionally add a short structured diagnostic log line (e.g.,
[DIAG] gh-status: missing) so monitoring or CI can detect the condition.
Acceptance criteria
- CI or test harness skips GH integration tests by default and runs them only when
RUN_GH_INTEGRATION=true and GITHUB_TOKEN (or gh auth) is present
- Tests cleanly report skipped when gate isn't enabled
- PR references this issue and parent #7687
Summary
Add CI gating for GitHub-integration tests (tests that require GH auth or network access) and small diagnostics/observability polish for the HealthService logs. (see parent issue #7687)
Motivation
Integration tests that require
ghor aGITHUB_TOKENshould be explicitly gated in CI to avoid flakiness. Separate this operational/CI-level work from the core HealthService bugfix to keep reviews focused.To do
RUN_GH_INTEGRATION=trueis set in the environment.[DIAG] gh-status: missing) so monitoring or CI can detect the condition.Acceptance criteria
RUN_GH_INTEGRATION=trueandGITHUB_TOKEN(or gh auth) is present