Skip to content

chore: add .editorconfig to all templates (fixes #152) - #168

Closed
emberb170d wants to merge 2 commits into
Create-Python-App:mainfrom
emberb170d:add-editorconfig
Closed

chore: add .editorconfig to all templates (fixes #152)#168
emberb170d wants to merge 2 commits into
Create-Python-App:mainfrom
emberb170d:add-editorconfig

Conversation

@emberb170d

Copy link
Copy Markdown
Contributor

Adds .editorconfig to all templates that are missing it (fixes#152)

FixesCreate-Python-App#152 - Add .editorconfig to all templates for consistent editor settings across projects.
All templates now have consistent indentation (space, 4), line endings (lf),
charset (utf-8), and trailing whitespace trimming.
@coderabbitai

Copy link
Copy Markdown

Warning

Review limit reached

@emberb170d, you've reached your PR review limit, so we couldn't start this review.

Next review available in:59 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b0edfdb8-fbf9-45f4-a9f6-39373fbde786

📥 Commits

Reviewing files that changed from the base of the PR and between 62aacc3 and 7ac456b.

📒 Files selected for processing (11)
  • templates/celery-worker/.editorconfig
  • templates/celery-worker/.python-version
  • templates/cli-starter/.editorconfig
  • templates/cli-starter/.python-version
  • templates/django-api/.editorconfig
  • templates/django-api/.python-version
  • templates/fastapi-starter/.editorconfig
  • templates/fastapi-starter/.python-version
  • templates/mlops-sklearn-starter/.editorconfig
  • templates/mlops-sklearn-starter/.python-version
  • templates/uv-workspace-starter/.editorconfig

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.

@ulises-jeremias

Copy link
Copy Markdown
Member

Closing as duplicate. .editorconfig and .python-version already landed on main in #159 (closes #152 / #153). This PR is also the same HEAD as #167. If we want the extra md / Makefile EditorConfig rules later, that should be a fresh branch from current main.

Sign up for freeto 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.

chore: add .editorconfig to all templates

2 participants

@emberb170d@ulises-jeremias