chore(ci): add commitlint config rules

[nanotaboada]

Summary by CodeRabbit

• Chores
  • Introduced a commit message linting configuration to enforce stricter formatting rules, with automatic exemptions for Dependabot-generated commits.

[coderabbitai]

Walkthrough

A new commitlint configuration file has been added. This configuration extends the conventional commitlint rules, enforces a maximum header and body line length of 80 characters, and introduces ignore rules to exempt Dependabot-generated commits from linting. The configuration is exported as the default export from the file.

Changes

File	Change Summary
commitlint.config.mjs	Added a commitlint configuration that extends conventional rules, sets 80-character limits, and ignores Dependabot commits.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant CommitLint

    Developer->>CommitLint: Submit commit message
    alt Dependabot commit (matches ignore rules)
        CommitLint-->>Developer: Skip linting
    else Non-Dependabot commit
        CommitLint->>CommitLint: Check header and body line lengths (max 80 chars)
        alt Passes rules
            CommitLint-->>Developer: Lint passes
        else Fails rules
            CommitLint-->>Developer: Lint fails with error
        end
    end

Loading

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00%	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (ecaf5fd)	1068	196	18.35%
Head commit (867fee6)	1068 (+0)	196 (+0)	18.35% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#225)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (4)

commitlint.config.mjs (4)

3-4: Consider using extends rather than spreading the base config
While spreading conventional works, it may inadvertently pull in internal keys. A more idiomatic approach is:

export default {
  extends: ["@commitlint/config-conventional"],
  rules: { /* ... */ },
  ignores: [ /* ... */ ]
};

This is clearer and prevents unexpected inheritance.

---

6-7: Revisit the 80-character body limit
Enforcing an 80-char max on commit bodies is stricter than the conventional default (100–120). Confirm with your team that this won’t break existing workflows or tooling.

---

13-13: Extend the Dependabot bump regex if needed
Your current pattern covers chore(deps): bump and chore(deps-dev): bump. If you also receive lockfile bumps, consider:

/(^chore\(deps(-dev)?\): bump |^chore\(lockfile\): )/

Adjust to fit your repo’s conventions.

---

15-15: Add a trailing newline
POSIX and many linters expect files to end with a newline.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ecaf5fd and 867fee6.

📒 Files selected for processing (1)

• commitlint.config.mjs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (csharp)