Skip to content

chore: add baseline .editorconfig#964

Merged
KooshaPari merged 1 commit into
mainfrom
chore/editorconfig-2026-04-27
Apr 26, 2026
Merged

chore: add baseline .editorconfig#964
KooshaPari merged 1 commit into
mainfrom
chore/editorconfig-2026-04-27

Conversation

@KooshaPari

@KooshaPari KooshaPari commented Apr 26, 2026

Copy link
Copy Markdown
Owner

User description

Adds repo-root .editorconfig with cross-editor defaults (UTF-8, LF, trailing-whitespace, 2-space default, 4-space rs/go/py, tab Makefile, md preserves trailing whitespace).

Wave-16 of cross-org bootstrap. API-only push.

Note

Low Risk
Low risk: adds editor formatting defaults only and does not change runtime code paths or behavior.

Overview
Adds a repo-root .editorconfig to standardize formatting across editors (UTF-8/LF, final newline, trim trailing whitespace, default 2-space indents). It also sets language-specific indentation overrides for *.rs/*.go/*.py, uses tabs for Makefile, and preserves trailing whitespace in *.md files.

Reviewed by Cursor Bugbot for commit 68fbbca. Bugbot is set up for automated code reviews on this repo. Configure here.


CodeAnt-AI Description

Add shared editor formatting rules for the repository

What Changed

  • Adds repo-wide formatting defaults for line endings, final newlines, trailing spaces, and 2-space indentation
  • Uses 4-space indentation for Rust, Go, and Python files
  • Uses tabs for Makefiles and keeps trailing spaces in Markdown files

Impact

✅ Fewer formatting differences across editors
✅ Cleaner diffs from line-ending changes
✅ Fewer Markdown formatting surprises

🔄 Retrigger CodeAnt AI Review

Details

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@codeant-ai

codeant-ai Bot commented Apr 26, 2026

Copy link
Copy Markdown

CodeAnt AI is reviewing your PR.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@coderabbitai

coderabbitai Bot commented Apr 26, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@KooshaPari has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 42 minutes and 54 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 42 minutes and 54 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 214e9e52-0180-46d0-b714-9fbbc5681584

📥 Commits

Reviewing files that changed from the base of the PR and between 1dde13c and 68fbbca.

📒 Files selected for processing (1)
  • .editorconfig

Note

.coderabbit.yaml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)
Validation error: Unrecognized key(s) in object: 'pre_merge_checks'
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • You can also validate your configuration using the online YAML validator.
  • 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
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/editorconfig-2026-04-27

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

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

@codeant-ai codeant-ai Bot added the size:S This PR changes 10-29 lines, ignoring generated files label Apr 26, 2026
@sonarqubecloud

Copy link
Copy Markdown

@cursor cursor 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.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix prepared a fix for the issue found in the latest run.

  • ✅ Fixed: Go files incorrectly configured to use spaces
    • Split the combined [.{rs,go}] section into separate [.go] and [*.rs] sections, with Go now correctly using indent_style=tab to match gofmt requirements.

Create PR

Or push these changes by commenting:

@cursor push 320cde890d
Preview (320cde890d)
diff --git a/.editorconfig b/.editorconfig
--- a/.editorconfig
+++ b/.editorconfig
@@ -8,9 +8,13 @@
 indent_style = space
 indent_size = 2
 
-[*.{rs,go}]
+[*.go]
+indent_style = tab
 indent_size = 4
 
+[*.rs]
+indent_size = 4
+
 [*.py]
 indent_size = 4

You can send follow-ups to the cloud agent here.

Reviewed by Cursor Bugbot for commit 68fbbca. Configure here.

Comment thread .editorconfig
indent_size = 2

[*.{rs,go}]
indent_size = 4

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Go files incorrectly configured to use spaces

Medium Severity

The [*.{rs,go}] section only overrides indent_size to 4 but inherits indent_style = space from the [*] section. Go universally uses tabs for indentation (enforced by gofmt), and this is a Go project with .go files throughout cmd/, internal/, and pkg/. Editors respecting this config will insert spaces into Go files, conflicting with gofmt and causing persistent formatting churn.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 68fbbca. Configure here.

@codeant-ai

codeant-ai Bot commented Apr 26, 2026

Copy link
Copy Markdown

CodeAnt AI finished reviewing your PR.

@KooshaPari KooshaPari merged commit fb343c3 into main Apr 26, 2026
9 of 12 checks passed
@KooshaPari KooshaPari deleted the chore/editorconfig-2026-04-27 branch April 26, 2026 21:42
@codeant-ai

codeant-ai Bot commented May 1, 2026

Copy link
Copy Markdown

CodeAnt AI is running the review.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added size:S This PR changes 10-29 lines, ignoring generated files and removed size:S This PR changes 10-29 lines, ignoring generated files labels May 1, 2026
@codeant-ai

codeant-ai Bot commented May 1, 2026

Copy link
Copy Markdown

Sequence Diagram

This PR introduces a repo-root editor configuration file that standardizes encoding, line endings, indentation, and whitespace handling across editors for this project.

sequenceDiagram
    participant Developer
    participant Editor
    participant EditorConfig

    Developer->>Editor: Open project file
    Editor->>EditorConfig: Load repo formatting rules
    EditorConfig-->>Editor: Return defaults and language overrides
    Developer->>Editor: Edit and save file
    Editor->>Developer: Apply standardized formatting on save
Loading

Generated by CodeAnt AI

@codeant-ai

codeant-ai Bot commented May 1, 2026

Copy link
Copy Markdown

CodeAnt AI finished running the review.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai

codeant-ai Bot commented May 1, 2026

Copy link
Copy Markdown

CodeAnt AI is running the review.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added size:S This PR changes 10-29 lines, ignoring generated files and removed size:S This PR changes 10-29 lines, ignoring generated files labels May 1, 2026
@codeant-ai

codeant-ai Bot commented May 1, 2026

Copy link
Copy Markdown

Sequence Diagram

This PR adds a repo-root editor configuration file so that different editors apply the same encoding, line endings, indentation, and whitespace rules when working in this project.

sequenceDiagram
    participant Developer
    participant Editor
    participant Repo

    Developer->>Editor: Open project files
    Editor->>Repo: Load editor configuration
    Repo-->>Editor: Return formatting rules
    Editor->>Editor: Apply formatting rules on save
    Editor-->>Developer: Show consistently formatted files
Loading

Generated by CodeAnt AI

@codeant-ai

codeant-ai Bot commented May 1, 2026

Copy link
Copy Markdown

CodeAnt AI finished running the review.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai

codeant-ai Bot commented May 2, 2026

Copy link
Copy Markdown

CodeAnt AI is running the review.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added size:S This PR changes 10-29 lines, ignoring generated files and removed size:S This PR changes 10-29 lines, ignoring generated files labels May 2, 2026
@codeant-ai

codeant-ai Bot commented May 2, 2026

Copy link
Copy Markdown

Sequence Diagram

This PR adds a root editor configuration file so that editors consistently apply charset, line endings, indentation, and whitespace rules across the repository, varying by file type. The diagram shows how a developer's edits are automatically normalized using the shared configuration before being saved to the repository.

sequenceDiagram
    participant Developer
    participant Editor
    participant Repository

    Developer->>Editor: Open or edit source file
    Editor->>Repository: Load editor configuration
    Repository-->>Editor: Return formatting rules by file type
    Editor->>Editor: Apply indentation and whitespace rules
    Developer->>Editor: Save file
    Editor->>Repository: Write normalized file content
Loading

Generated by CodeAnt AI

@codeant-ai

codeant-ai Bot commented May 2, 2026

Copy link
Copy Markdown

CodeAnt AI finished running the review.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai

codeant-ai Bot commented May 2, 2026

Copy link
Copy Markdown

CodeAnt AI is running the review.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added size:S This PR changes 10-29 lines, ignoring generated files and removed size:S This PR changes 10-29 lines, ignoring generated files labels May 2, 2026
@codeant-ai

codeant-ai Bot commented May 2, 2026

Copy link
Copy Markdown

Sequence Diagram

This PR introduces a repo-root editor configuration file that standardizes encoding, line endings, indentation, and whitespace handling across file types when developers edit this repository.

sequenceDiagram
    participant Developer
    participant Editor
    participant EditorConfig

    Developer->>Editor: Open project and file
    Editor->>EditorConfig: Load repo editor configuration
    EditorConfig-->>Editor: Return global formatting rules
    Editor->>EditorConfig: Resolve rules for current file type
    EditorConfig-->>Editor: Return indentation and whitespace settings
    Editor-->>Developer: Apply formatting while editing
Loading

Generated by CodeAnt AI

@codeant-ai

codeant-ai Bot commented May 2, 2026

Copy link
Copy Markdown

CodeAnt AI finished running the review.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

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

Labels

size:S This PR changes 10-29 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant