Skip to content

Add .editorconfig with default Visual Studio values#165

Draft
Copilot wants to merge 2 commits intomasterfrom
copilot/add-editorconfig-visual-studio-2026
Draft

Add .editorconfig with default Visual Studio values#165
Copilot wants to merge 2 commits intomasterfrom
copilot/add-editorconfig-visual-studio-2026

Conversation

Copy link
Contributor

Copilot AI commented Feb 24, 2026

The repository had no .editorconfig, leaving editor formatting behavior undefined across contributors.

Changes

  • Added .editorconfig at the repository root with standard Visual Studio defaults for a C#/.NET project, covering:
    • All files – space indentation
    • C#/VB files – 4-space indent, UTF-8 BOM, final newline
    • XML project/config files – 2-space indent
    • JSON files – 2-space indent
    • Dotnet styleSystem.* usings first, no this. qualification, language keywords preferred, modern language feature suggestions
    • C# stylevar preference, Allman brace style, expression-body rules, pattern matching suggestions, indentation/spacing/wrapping conventions

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • learn.microsoft.com
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:


🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Co-authored-by: gehnster <7077730+gehnster@users.noreply.github.com>
Copilot AI changed the title [WIP] Add .editorconfig with default Visual Studio 2026 values Add .editorconfig with default Visual Studio values Feb 24, 2026
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