Skip to content

The hub's own .editorconfig comment contradicts CODESTYLE.md's whole-file carry model #988

Description

@ptr727

What happened

.editorconfig carries this comment above the .NET-only block, on current hub main:

# .NET-only below, covering C# and ReSharper style.
# Everything above is the line-ending governance every derived repo carries, and a non-.NET repo may drop from here down.

CODESTYLE.md "General" states the opposite -- that the whole file, including inert language-specific blocks, is kept rather than trimmed:

A repo keeps the whole file rather than trimming it. An unused-language section costs nothing, the same whole-file model as .editorconfig, whose inert [*.cs] block a non-.NET repo keeps.

So the two hub-canonical files disagree about the intended behavior for a non-.NET repo: one says "may drop", the other says "keeps... doesn't trim." This reads like leftover text from before #160 settled on the whole-file model -- the comment inside .editorconfig itself was never updated to match.

Where I hit it

Resyncing ptr727/HomeAutomation-Config (source-only, no .NET): I re-vendored .editorconfig to match the hub's current file byte-for-byte per the whole-file model CODESTYLE.md states (restoring the previously-trimmed .NET/ReSharper block). CodeRabbit flagged the contradiction against the very comment I was re-vendoring (PR #76, .editorconfig:44). Declined there as hub-owned verbatim content I can't fix locally without diverging from the hub's canonical file -- filing here instead.

Suggested fix

Reword the comment to state the file is kept whole regardless of language mix, e.g. "a non-.NET repo carries this section unused, per CODESTYLE.md's whole-file model" instead of "may drop from here down."

audit run 2026-08-25T13:46:24Z | hub fa63163

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions