Skip to content

ci: enforce EditorConfig for YAML files - #18712

Draft
Tobias Brick (tobiasb-ms) wants to merge 2 commits into
4.0from
tobiasb-ms/enforce-yaml-editorconfig
Draft

ci: enforce EditorConfig for YAML files#18712
Tobias Brick (tobiasb-ms) wants to merge 2 commits into
4.0from
tobiasb-ms/enforce-yaml-editorconfig

Conversation

@tobiasb-ms

Copy link
Copy Markdown
Contributor

Extend the existing pre-commit EditorConfig check to .yml and .yaml files and document the expanded scope.

Copilot AI balanced review requested due to automatic review settings September 4, 2026 15:56

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

An existing YAML file violates the newly enforced final-newline rule, causing CI to fail.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Extends EditorConfig enforcement to YAML files and updates contributor guidance.

Changes:

  • Adds .yml and .yaml to the pre-commit check.
  • Documents the expanded validation scope.
File summaries
File Description
.pre-commit-config.yaml Expands the EditorConfig file filter.
CONTRIBUTING.md Documents YAML validation.
Review details
  • Files reviewed: 2/2 changed files
  • Comments generated: 1
  • Review effort level: Balanced

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .pre-commit-config.yaml
hooks:
- id: editorconfig-checker
files: '\.toml$'
files: '\.(toml|ya?ml)$'

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

[Perihelion🚀] Correct. I normalized .pipelines/CodeQL/CodeQL.yml in a separate commit so the existing violation remains explicit and independently reviewable: 60352bd8f7.

Copilot AI review requested due to automatic review settings September 4, 2026 19:47

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟢 Approval recommended

The filter correctly covers both YAML extensions, and all affected files satisfy the configured rules.

Review details
  • Files reviewed: 2/3 changed files
  • Comments generated: 0 new
  • Review effort level: Balanced

@tobiasb-ms

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.

Extend the existing pre-commit check so YAML files follow the repository-wide EditorConfig rules.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings September 4, 2026 22:56
@tobiasb-ms
Tobias Brick (tobiasb-ms) force-pushed the tobiasb-ms/enforce-yaml-editorconfig branch from 60352bd to d7ab293 Compare September 4, 2026 22:56
@tobiasb-ms
Tobias Brick (tobiasb-ms) marked this pull request as ready for review September 4, 2026 22:57
@tobiasb-ms
Tobias Brick (tobiasb-ms) requested a review from a team as a code owner September 4, 2026 22:57
@tobiasb-ms
Tobias Brick (tobiasb-ms) marked this pull request as draft September 4, 2026 22:57

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟢 Approval recommended

The expanded check is correctly configured and all included YAML files satisfy the repository’s EditorConfig rules.

Review details
  • Files reviewed: 2/3 changed files
  • Comments generated: 0 new
  • Review effort level: Balanced

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

2 participants