Skip to content

chore: add DeepSource configuration - #1

Open
2233admin wants to merge 2 commits into
masterfrom
chore/deepsource-config-20260623183602
Open

2233admin wants to merge 2 commits into
masterfrom
chore/deepsource-config-20260623183602

Conversation

@2233admin

Copy link
Copy Markdown
Owner

Summary

  • Add repository-local DeepSource configuration.
  • Enabled analyzers: python.
  • Exclude generated, dependency, and build output paths to keep first-run findings actionable.

Validation

  • Parsed .deepsource.toml with Python tomllib.
  • Existing CI/CodeQL/Dependabot configuration is unchanged.

Follow-up

  • Enable 2233admin/cli2skill in the DeepSource Dashboard after this PR merges.
  • Review first analysis and tune exclude_patterns if generated files dominate findings.

@coderabbitai

coderabbitai Bot commented Jun 23, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: efb0bb0f-f074-42a7-9a4e-3564e3202373
📥 Commits

Reviewing files that changed from the base of the PR and between 80b50be and 585f13c.

📒 Files selected for processing: 2
  • .deepsource.toml
  • .github/workflows/ci.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Summary

Summary by CodeRabbit

  • Chores
    • Added automated checks for Python code style and complexity.
    • Updated CI to use an alternate runner for eligible pushes, workflow runs, and pull requests; other runs continue to use the standard runner. These changes do not affect app functionality.

The pull request adds a DeepSource configuration for Python analysis. It also changes the CI test job to select a runner based on the enablement variable, event type, and repository conditions.

Changes: DeepSource configuration

Layer / File(s) Summary
Python analyzer settings
.deepsource.toml
Adds test and exclusion patterns. Enables the Python analyzer with runtime 3.x.x, maximum line length 120, and cyclomatic complexity threshold high.

CI runner selection

Layer / File(s) Summary
Conditional test runner
.github/workflows/ci.yml
Uses ci-5070x-linux when the enablement variable is 'true' and the event and repository conditions match. Otherwise, uses ubuntu-latest.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 585f1

This PR adds a DeepSource configuration and optionally routes same-repository CI runs to a dedicated runner, which is opt-in via a repository variable. No concrete merge-blocking defect was found. Before enabling the variable, confirm the dedicated runner is ephemeral and isolated.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly identifies the primary change: adding a DeepSource configuration. It is concise and related to the changeset.
Description check Passed The description is directly related to the DeepSource configuration and validation work. It does not mention the CI runner change and incorrectly states that CI configuration is unchanged, but it is n…
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The description is directly related to the DeepSource configuration and validation work. It does not mention the CI runner change and incorrectly states that CI configuration is unchanged, but it is not off-topic.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

A rabbit checks the Python lines,
Then picks a runner when it aligns.
If conditions match, the new path is clear,
Else ubuntu-latest will appear.
Hop, hop—the checks proceed from here.

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a .deepsource.toml configuration file to enable the DeepSource Python analyzer. The review feedback recommends specifying a concrete Python version (such as "3.10") for the runtime_version setting instead of "3.x.x" to ensure proper syntax parsing and compatibility.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread .deepsource.toml
enabled = true

[analyzers.meta]
runtime_version = "3.x.x"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The runtime_version is set to "3.x.x". DeepSource's Python analyzer expects a specific major.minor version (e.g., "3.10", "3.11"). Since the project's pyproject.toml specifies requires-python = ">=3.10", setting this to "3.10" ensures the analyzer parses the code using a compatible Python version and avoids potential syntax parsing errors.

Suggested change
runtime_version = "3.x.x"
runtime_version = "3.10"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant