chore: delete the Go Report Card workflow - #488
Merged
Merged
Conversation
The badge came out of the README when goreportcard.com was sunset. The workflow that fed it stayed, and it has been running on every push to main since, posting to a service that no longer exists. It reports success either way. `creekorful/goreportcard-action` fires the request and never checks the response, so a dead endpoint is indistinguishable from a working one. Nothing would ever have surfaced this. Nothing replaces it. golangci-lint already runs in CI with a stricter set than Go Report Card graded on, and the build badge carries that claim. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #488 +/- ##
=======================================
Coverage 99.94% 99.94%
=======================================
Files 484 484
Lines 22877 22877
=======================================
Hits 22865 22865
Misses 12 12 Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
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
1 participant
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.
The badge came out of the README when goreportcard.com was sunset. The workflow
that fed it stayed, and it has been running on every push to
mainever since,posting to a service that no longer exists.
It reports
successeither way. The action fires the request and neverchecks the response, so a dead endpoint looks identical to a working one.
Nothing would ever have surfaced this — it was found by comparing workflow
triggers across the org, not by a failure.
Last runs before this PR: gohai 2026-09-12, osapi 2026-09-09, nats-client
2026-09-07, nats-server 2026-09-07, osapi-orchestrator 2026-09-07. All green,
all pointless.
Nothing replaces it
golangci-lintalready runs in CI with a stricter set than Go Report Cardgraded on, and
it publishes no score badge by design
because a meta-linter's grade only describes which linters you enabled. The
build badge carries the claim.
Same deletion in all five Go repos.
🤖 Generated with Claude Code
https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c