pre-commit fighting with itself.

[JNygaard-Skylight]

Description

pre-commit appears to use different rules when ran locally and when ran in the Github pipeline. Example: This PR. In particular see commit b538b3f and commit d997b7a

Steps to reproduce

1. Locally run `pre-commit run --all-files and commit changes
2. Create a PR.
3. pre-commit should then make autofixes that overwrite some of the changes made locally similar to the example above.

Expected Result

In the Github Actions pre-commit should not overwrite changes it makes locally.

Actual result

Github Actions pre-commit is overwriting changes it makes locally (see example above).

Priority

Provide an estimate for level of impact the bug has today by placing an X in the applicable bracket

Priority

• Low priority The bug does not have to be fixed immediately. High and medium priority bugs should be addressed first.
• Medium priority Typically, medium-priority bugs do not affect customers directly and therefore can be fixed in the normal course of testing and development.
• High priority High priority bugs must be addressed immediately. They often affect the app’s functionality and impact customers and their user experience. They must take priority.