ci: update linter

[calebephrem]

No description provided.

[vercel]

@calebephrem is attempting to deploy a commit to the calebephrem's projects Team on Vercel.

A member of the Team first needs to authorize it.

[beetle-ai]

Summary by Beetle

This PR significantly expands the linter configuration for the repository by enabling comprehensive validation across multiple programming languages and file formats. The change replaces a minimal linter setup (which had most validators disabled) with an extensive multi-language validation strategy that covers 30+ different file types and languages including Python, JavaScript/TypeScript, Go, Rust, Java, Kotlin, Bash, Docker, Terraform, Kubernetes, and various markup/config formats.

📁 File Changes Summary (Consolidated across all commits):

File	Status	Changes	Description
.github/workflows/linter.yaml src/templates/linter.yml	Modified	+62/-20	Replaced minimal linter configuration with comprehensive multi-language validation. Removed 10 disabled validators (including ENABLE_GITHUB_PULL_REQUEST_SUMMARY_COMMENT, VALIDATE_SPELL_CODESPELL, VALIDATE_NATURAL_LANGUAGE, VALIDATE_MARKDOWN, VALIDATE_BIOME*, VALIDATE_JSCPD, VALIDATE_GITHUB_ACTIONS_ZIZMOR) and added 31 enabled validators covering Python, JavaScript/TypeScript, Go, Rust, Java, Kotlin, Bash, JSON, YAML, XML, Docker, Terraform, Kubernetes, Ansible, GitHub Actions, and Prettier formatting for multiple file types.

Total Changes: 2 files changed, +62 additions, -20 deletions

🎯 Key Changes:

• Comprehensive Language Support: Enabled linting for 10+ programming languages (Python with Pylint & Ruff, JavaScript/TypeScript, Go with modules, Rust Clippy, Java, Kotlin, Bash)
• Infrastructure as Code Validation: Added validation for Docker (Hadolint), Terraform (TFLint), Kubernetes (Kubeconform), and Ansible
• Configuration File Validation: Enabled validation for JSON, YAML, XML, and ENV files
• Prettier Integration: Enabled Prettier formatting validation for 11 file types (CSS, GraphQL, HTML, JavaScript, JSON, JSONC, JSX, Markdown, TypeScript, Vue, YAML)
• Security & Quality: Added Git merge conflict marker detection and GitHub Actions validation
• Removed Features: Disabled PR summary comments, spell checking, natural language validation, Biome linting, JSCPD (copy-paste detection), and Zizmor GitHub Actions security scanning

📊 Impact Assessment:

• Security: Mixed impact - adds validation for infrastructure files (Docker, Terraform, Kubernetes) and GitHub Actions which improves security posture, but removes Zizmor security scanning for GitHub Actions. The addition of merge conflict detection prevents accidental commits of unresolved conflicts. Overall positive for catching configuration vulnerabilities.
• Performance: Significant performance impact expected - the linter will now run 31 validators instead of the previous minimal set. CI/CD pipeline execution time will increase substantially, especially on larger codebases. Consider implementing caching strategies or parallel execution to mitigate slowdowns.
• Maintainability: Greatly improved - standardized code formatting and linting across multiple languages will enforce consistent code quality standards. The comprehensive validation will catch issues earlier in the development cycle. However, the team must ensure all required linters are properly configured and maintained. The removal of ENABLE_GITHUB_PULL_REQUEST_SUMMARY_COMMENT: false (now defaults to enabled) may provide helpful feedback to developers.
• Testing: Enhanced quality assurance - the expanded linter coverage acts as an additional testing layer, catching syntax errors, style violations, and potential bugs before code review. The validation of test files themselves (if written in covered languages) will improve test code quality. Teams should ensure linter rules align with project standards to avoid false positives that could slow down development.

⚙️ Settings

Severity Threshold: Medium — Balanced feedback — medium and high severity issues only. — Change in Settings
Custom Rules: Define your own review rules — Set Custom Rules
PR Summary: Configure PR summary — Change in Settings

📖 User Guide

• Once repos are connected, PR analysis is automatically enabled. You can disable analysis for this repo from beetleai.dev/analysis
• Comment @beetle on any PR to start analysis manually
• Comment @beetle stop to stop any ongoing analysis

---

Follow us: Beetle · X · LinkedIn

[beetle-ai]

✅ You're good to merge this PR! No issues found. Great job!

Settings

⚙️ Settings

Severity Threshold: Medium — Balanced feedback — medium and high severity issues only. — Change in Settings
Custom Rules: Define your own review rules — Set Custom Rules
PR Summary: Configure PR summary — Change in Settings

📖 User Guide

• Once repos are connected, PR analysis is automatically enabled. You can disable analysis for this repo from beetleai.dev/analysis
• Comment @beetle on any PR to start analysis manually
• Comment @beetle stop to stop any ongoing analysis