Introduce an extremely simplistic .pre-commit-config.yaml file
#348
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit merges an extremely simplistic
.pre-commit-config.yamlfile that applies some extremely simplistic checks. The intention to merge this commit into the main branch while we configure pre-commit to run code formatting/linting in the newchem-cpp branch. PR #287 (where we start configuring pre-commit to run formatting/linting) is configured so all changes build off this commit (in other words, there won't be any merge conflicts when we ultimately merge newchem-cpp into main).If we don't merge a .pre-commit-config.yaml file into the main branch, then pre-commit.ci will report a failure (since it can't find a .pre-commit-config.yaml file)
In slightly more detail, the file configures pre-commit to check that