fix: resolve mega-linter failure from invalid .editorconfig EOF/newline state#83
Conversation
Co-authored-by: devantler <26203420+devantler@users.noreply.github.com>
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts
|
There was a problem hiding this comment.
Pull request overview
This PR adds a repository-level .editorconfig intended to satisfy MegaLinter’s EDITORCONFIG_EDITORCONFIG_CHECKER requirements (LF line endings + final newline) and establish baseline formatting defaults across editors.
Changes:
- Added a root
.editorconfigdefining UTF-8, LF, trimming trailing whitespace, and requiring a final newline. - Added language-specific indentation rules for Go and YAML/JSON/Markdown.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@copilot fix or exempt the remaining markdown lint issues: .claude/skills/maintain/SKILL.md:5 error MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "Perform maintenance per the **..."] |
Co-authored-by: devantler <26203420+devantler@users.noreply.github.com>
Addressed in
Targeted markdownlint validation now passes for the requested rules on the affected files. |

The
🧹 Lint - mega-linterjob failed onEDITORCONFIG_EDITORCONFIG_CHECKERdue to.editorconfignot satisfying newline/line-ending requirements. This PR adds a compliant.editorconfigso the lint step can pass.Root-cause correction
.editorconfigwith valid LF endings and a required final newline.EditorConfig baseline
utf-8,lf, trailing whitespace trim, final newline).