If this is still relevant, I would think because for languages that don't have strict rules on line length, using linting settings in a collaborative environment would cause things like comments changes and unnecessary commit changes.
Example: I use a desktop, personal laptop, and work laptop to work on personal projects. While I plan to, I haven't yet amalgamated all the different user settings. As a result, a Python file, for example, might get added to a commit solely because the linter on the work laptop is set to 80 and on the personal to 75. This could cause the docstrings describing the various functions in that file to be "re-arranged". While I might make an actual change to that file, when I save at the line length change is applied to the docstrings, those changes will also get pushed.
Now, imagine this amongst a whole team! Unless an organization or team leader sets out specific style guidelines and enforces it so everyone is using the same settings file, this could cause a very messy commit history.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How so/why not? <--curious, not argumentative. :)
If this is still relevant, I would think because for languages that don't have strict rules on line length, using linting settings in a collaborative environment would cause things like comments changes and unnecessary commit changes.
Example: I use a desktop, personal laptop, and work laptop to work on personal projects. While I plan to, I haven't yet amalgamated all the different user settings. As a result, a Python file, for example, might get added to a commit solely because the linter on the work laptop is set to 80 and on the personal to 75. This could cause the docstrings describing the various functions in that file to be "re-arranged". While I might make an actual change to that file, when I save at the line length change is applied to the docstrings, those changes will also get pushed.
Now, imagine this amongst a whole team! Unless an organization or team leader sets out specific style guidelines and enforces it so everyone is using the same settings file, this could cause a very messy commit history.