Skip to content

t4346: fix Codacy CI failures - add .codacy.yml config #4364

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alex-solovyev merged 1 commit into from
Mar 13, 2026
Merged

t4346: fix Codacy CI failures - add .codacy.yml config #4364

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions .codacy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Codacy Static Analysis Configuration
# Aligns Codacy's analysis with the project's existing shellcheck and quality settings.
#
# Reference: https://docs.codacy.com/repositories-configure/codacy-configuration-file/
#
# Root cause context (GH#4346):
# - Codacy flagged SC2086 (unquoted variable) in code that was being REMOVED by a PR fix.
# - Codacy also returned "not_collected" on a transient service issue.
# - This config excludes archived/ (same as CI shellcheck) and aligns tool settings.

---
engines:
shellcheck:
enabled: true
semgrep:
enabled: true
trivy:
enabled: true
pylint:
enabled: true
eslint:
enabled: true

exclude_paths:
# Archived code is versioned for reference but not actively maintained.
# Matches the shellcheck exclusion in .github/workflows/code-quality.yml.
- "archived/**"
# Generated/vendor files
- "node_modules/**"
- ".git/**"
# Config templates (not executable code)
- "configs/*.json.txt"
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The current exclusion pattern configs/*.json.txt only matches files directly within the configs/ directory. If config templates are ever added to subdirectories (e.g., configs/staging/settings.json.txt), they will not be excluded from analysis. To make this rule more robust and future-proof, consider using a recursive glob pattern.

  - "configs/**/*.json.txt"

Loading