Repository navigation
Add maintainer-run integration connectivity check workflow - #209
Merged
AndreasIgel merged 5 commits intoJul 20, 2026
Merged
AndreasIgel merged 5 commits into
AndreasIgel merged 5 commits into
Conversation
Co-Authored-By: Andreas Igel <andreas.igel@computacenter.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…y check Co-Authored-By: Andreas Igel <andreas.igel@computacenter.com>
Co-Authored-By: Andreas Igel <andreas.igel@computacenter.com>
Co-Authored-By: Andreas Igel <andreas.igel@computacenter.com>
Co-Authored-By: Andreas Igel <andreas.igel@computacenter.com>
This was referenced Jul 20, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
integrations-check.yml, a maintainer-onlyworkflow_dispatchdiagnostic that verifies the 3rd-party integration secrets and endpoints in seconds — without building or running any project/PR code. Motivated by the fork Sonar publish failing withHTTP 403 ... check SONAR_TOKEN, where a full CI run was a slow/noisy way to discover a token problem.Fixes #208Input
target:all/sonarcloud/codecov.What it checks
SONAR_TOKENpresent + valid viaGET https://sonarcloud.io/api/authentication/validate(token as basic-auth username; value never printed). Fails on403/"valid":false.CODECOV_TOKEN(the repo upload token) present + accepted by the first step of Codecov's upload handshake:POST https://api.codecov.io/upload/github/<owner>::::<repo>/commitswithAuthorization: token …against the realGITHUB_SHA(the same create-commit call the uploader makes).Codecov result mapping:
200/201= token authenticates;401/403= token rejected;404= authenticated but repo not set up / not visible; other = reachability/service issue. Temp files use$RUNNER_TEMP.Why it's safe
workflow_dispatchis startable only by write-access users from the default branch → inherently maintainer-gated, never runs for fork PRs.set -euo pipefail, tokens confined to env/auth header/basic-auth). The upload create-commit call targets the real HEAD commit, so it adds no spurious data.Scope
Single new workflow file; nothing else touched. Diagnostic only — does not replace the
fork-cienvironment approval that gates the actual Sonar publish.Maintainer TODOs
SONAR_TOKEN/CODECOV_TOKEN— this should surface the current Sonar403.