Add .editorconfig to standardize formatting across contributions#671
Open
Add .editorconfig to standardize formatting across contributions#671
Conversation
Agent-Logs-Url: https://github.com/microsoft/apm/sessions/61b89d0e-2a7c-4151-9038-3901de393295 Co-authored-by: sergio-sisternes-epam <207026618+sergio-sisternes-epam@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add .editorconfig to standardize formatting across contributions
Add .editorconfig to standardize formatting across contributions
Apr 10, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a repository-root .editorconfig to standardize basic formatting across editors, reducing noise in diffs and making contributions more consistent across the codebase.
Changes:
- Introduces a root
.editorconfigwith consistent defaults (LF, final newline, trimming whitespace, 4-space indent). - Adds filetype-specific overrides (2-space indent for YAML/JSON/Markdown; preserve Markdown trailing spaces; tabs for Makefile).
sergio-sisternes-epam
approved these changes
Apr 10, 2026
Collaborator
sergio-sisternes-epam
left a comment
There was a problem hiding this comment.
Validated against the codebase: 4-space Python, 2-space YAML/JSON/MD, LF line endings, UTF-8 — all match existing conventions. Clean isolated config, no files modified. LGTM.
|
If you want to require a particular line ending for a file type you may also need to update Alternatively, it may be interesting to...
|
Collaborator
|
@copilot review feedback |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Without a
.editorconfig, contributors' editors apply inconsistent formatting (trailing whitespace, final newlines, indent style), inflating diffs and making reviews harder. Adds a root.editorconfigso editors enforce consistent defaults automatically.Settings:
charset = utf-8,end_of_line = lf,insert_final_newline = truetrim_trailing_whitespace = trueglobally;falsefor*.md(trailing spaces are semantic in Markdown — they produce<br>)indent_style = space,indent_size = 4globally (Python, shell, etc.)indent_size = 2for*.yml,*.yaml,*.json,*.mdindent_style = tabforMakefile(required bymake)No existing files modified — isolated to the new config file only.
Type of change
Testing