Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I am very guilty of this and have tons of commits where some small linter change from vscode ends up causing a build to fail. I propose we add a pre-commit check file that can optionally be used by developers to prevent so many silly commits for just fixing linter issues. I know I would benefit from this greatly.
Describe the solution you'd like
.pre-commit-config.yaml file with the same configurations that are used in CI to help limit commits that ultimately fail in CI linter checks. This should be optional and not forced on the developer if they choose not to use it.
Describe alternatives you've considered
None
Additional context
None
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I am very guilty of this and have tons of commits where some small linter change from vscode ends up causing a build to fail. I propose we add a pre-commit check file that can optionally be used by developers to prevent so many silly commits for just fixing linter issues. I know I would benefit from this greatly.
Describe the solution you'd like
.pre-commit-config.yaml file with the same configurations that are used in CI to help limit commits that ultimately fail in CI linter checks. This should be optional and not forced on the developer if they choose not to use it.
Describe alternatives you've considered
None
Additional context
None