Closed KOLANICH closed 4 years ago
I'm +0 as my editors (vim and VS Code) don't use that file, but if it helps others I don't really mind. But let's not turn it into a place for style battlegrounds :-)
In fact there are plugins: https://github.com/editorconfig/editorconfig-vim https://github.com/editorconfig/editorconfig-vscode
Thank you! That's interesting to know, although I don't expect I'll use them as my personal config seems to match fine with what I need on the projects I work on. But it's good to know for future.
Closing since we closed #7733.
@KOLANICH Please add "Related to #
Ah, thank you, I did not look in the commit message itself for an issue reference. I think my justification was pretty strong but if anyone thinks otherwise please say so!
Another note @KOLANICH, when mentioning issues it's usually a good idea NOT to mention them in the git commit title/description itself since that tends to spam the issue when rebasing/amending commits. Just the body of the PR message is OK.
I am +1 to adding an
.editorconfig
since there’s no obvious downside. What goes in it would need more discussion.