Repository navigation
fix(ci): ignore vendored TODO comments - #6708
Conversation
✅MegaLinter analysis: Success✅ Linters with no issuesactionlint, bash-exec, git_diff, hadolint, jscpd, jsonlint, lychee, markdown-table-formatter, markdownlint, prettier, prettier, shellcheck, shfmt, stylelint, syft, trivy-sbom, trufflehog, v8r, v8r, yamllint Notices
See detailed reports in MegaLinter artifacts
|
|
Consider upstreaming filtering instead of this. That way we keep the integration pure. |
@coderabbitai review |
|
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📜 Recent review details🧰 Additional context used📓 Path-based instructions (4)Use Go 1.26.1 or newer, matching the version declared in `go.mod`.📄 CodeRabbit inference engine (AGENTS.md) Files:
Generated files must not be hand-edited; run `make generate` as the canonical regeneration command.📄 CodeRabbit inference engine (AGENTS.md) Files:
Validate workflow changes with `mega-linter-runner -f go`; MegaLinter runs `actionlint` for GitHub Actions workflows.📄 CodeRabbit inference engine (AGENTS.md) Files:
Add regression tests for confident bug fixes and run flaky-test candidates repeatedly with `go test -run -count=10 ./...`.📄 CodeRabbit inference engine (AGENTS.md) Files:
🔇 Additional comments (2)
📝 WalkthroughWalkthroughThe Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error, 1 warning)
✅ Passed checks (3 passed)
Full details: Linked Issues checkExplanation The changes satisfy issue Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Resolved CodeRabbit's Linked Issues check: issue #6707 is the sole close target. The PR body now describes scanner-created artifacts 6688 through 6702 without linking them, because their cleanup is intentionally deferred until this prevention merges and a post-merge scan proves they cannot recur. The optional docstring warning does not require a code change: the only new function is Go's |
@coderabbitai review |
|
|
I evaluated the upstream option. The current task constraint is a KSail-only downstream repair, and the shared v13.2.1 workflow exposes no User evaluation at exact head |

Summary
^third_party/path filter so vendoredgo-archivecomments cannot create KSail issuesFixes #6707.
Root cause
The scanner supports a file-path ignore expression, but
devantler-tech/actionsv13.2.1's reusable workflow and composite interface do not expose it. KSail therefore scannedthird_party/go-archiveas maintained source and opened scanner-created issues 6688–6702 from upstream comments.This change stays downstream-only as requested; it does not alter the shared actions contract.
Verification
RED first:
TestTODOScannerExcludesOnlyVendoredSourcesfailed because the reusable job could not deliver a KSail-specific scanner inputGREEN on commit
8f8161fb4fb14215a3cb08278a42971f8d63ff49:go test ./internal/ciharnessgolangci-lint:0 issuesactionlint .github/workflows/todos.yamlzizmor .github/workflows/todos.yaml: no findingsgit diff --checkThe full
go test ./...run produced no failure output but did not terminate inside the bounded local window, so complete repository proof remains with required CI.Remaining gate
Keep this draft until required CI, current-head review, and user evaluation are green. Close scanner-created issues 6688–6702 and remove their Project 5 items only after this prevention is merged and a post-merge scanner run confirms they cannot be recreated.