Run the lint gate on pushes to main so defects cannot land silently #2779

Activity

1. github-project-automation

   added this to 🌊 Project Boardon Jul 21, 2026
2. devantler

   added the

   Chore

   issue type on Jul 21, 2026
3. devantler

   added a parent issue on Jul 21, 2026

   • Lint gate is red on every pull request, and main never runs it #2775
4. devantler

   marked this as blocked by 2 issues on Jul 21, 2026

   • Duplication scanner still reports clones in the EKS validator tests #2777
   • Two Python test files keep the duplication scanner red #2778
5. devantler

   moved this to 📥 Backlog in 🌊 Project Boardon Jul 21, 2026
6. devantler commented on Jul 21, 2026

   

   devantler

   on Jul 21, 2026

   ContributorAuthor

   More actions

   🤖 Generated by the Daily AI Engineer

   Closing — the premise is wrong, and acting on it would have made things worse.

   I filed this believing the lint job's absence from main was the root cause, so switching it on there looked like the durable fix. #2780 inventoried the whole job and showed otherwise: the baseline currently carries thousands of findings (8051 cspell, 287 checkov, 166 lychee, and more), most of them misconfiguration rather than defects. Running that against main would not have caught anything early — it would have turned main red on day one and left it that way.

   The real cause is that the job is paths-filtered onto the Go validation path, so it is skipped by the k8s/** changes that make up almost every PR here, and the red baseline only surfaces for the rare PR touching something else. #2780 has the correct shape for the fix: disposition each linter explicitly and scope them to changed files, without silencing anything security-relevant.

   Superseded by #2780.
7. devantler

   closed this as not plannedon Jul 21, 2026
8. github-project-automation

   moved this from 📥 Backlog to ✅ Done in 🌊 Project Boardon Jul 21, 2026
9. coderabbitai commented on Jul 21, 2026

   

   coderabbitaiBot

   on Jul 21, 2026 – with coderabbitai

   Contributor

   More actions

   🔗 Related PRs

   #2339 - docs(agents): record merge-queue mechanics + root-cause-before-requeue [merged]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!