chore: add .editorconfig for consistent code formatting#2366
chore: add .editorconfig for consistent code formatting#2366srpatcha wants to merge 1 commit intogithub:mainfrom
Conversation
mnriem
left a comment
There was a problem hiding this comment.
It looks like you are mixing two PRs?
|
Hi @mnriem, you're right — this PR has grown beyond the initial .editorconfig scope. I'll split it into separate PRs:
I'll restructure and resubmit. Thank you for the feedback! |
eaba366 to
f6abe06
Compare
|
Hi @mnriem, I've restructured the PR to contain only the .editorconfig change as originally described. The validation workflow step has been removed and will be submitted as a separate focused PR. Ready for re-review! |
There was a problem hiding this comment.
Pull request overview
This PR adds a root .editorconfig to standardize editor behavior in the spec-kit repository, complementing the repo’s existing formatting/linting setup.
Changes:
- Adds global defaults for LF line endings, final newlines, UTF-8, and trailing-whitespace trimming.
- Adds file-type-specific rules for Python, YAML, Markdown, and Makefiles.
Show a summary per file
| File | Description |
|---|---|
.editorconfig |
Introduces repository-wide editor defaults and per-file-type formatting settings. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 2
| indent_size = 2 | ||
|
|
||
| [*.md] | ||
| trim_trailing_whitespace = false |
| [*.{yml,yaml}] | ||
| indent_style = space | ||
| indent_size = 2 | ||
|
|
|
Please address Copilot feedback |
Changes
chore: add .editorconfig for consistent code formatting
Signed with GPG.