add pre-commit, other development setup stuff #113
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.
Based on my experience with #112, this proposes some changes to improve the experience of developing on this repo, and to improve our release confidence in changes.
pre-commit
configurationpre-commit
over all the files.gitignore
to prevent unwanted files from making it into source controlNotes for Reviewers
Any changes to scripts in the
colab/
directory were made automatically like this:I'll propose a follow-up PR after this adding the
ruff
linter to more thoroughly check the source code. But wanted to do the rest of this first to make the changes easier to review.