gha: upgrade to `actions/cache@v5` (#455)Updated the pre-commit GitHub actions workflow to use version 5https://github.com/actions/cache/releases/tag/v5.0.0
Clean up the pre-commit workflow (#447)Rename file, use "color" always, install from requirements file, adjust name key
Bump `actions/checkout` to `v6` (#446)https://github.com/actions/checkout/releases/tag/v6.0.0
linter.yml: bump `actions/cache` and `actions/checkout` (#408)Both actions moved up one version https://github.com/actions/checkout https://github.com/actions/cache
Add pre-commit hook to auto insert license headers for Markdown (#394)Ran the hook the first time it auto inserted the license headers and failed.Second time ran the hook it passed and no files w
Add pre-commit hook to auto insert license headers for Markdown (#394)Ran the hook the first time it auto inserted the license headers and failed.Second time ran the hook it passed and no files were change.The Lucas-C hooks are used on both Airflow and Sedona.
show more ...
Standardize the pre-commit config (#253)https://github.com/codespell-project/codespell?tab=readme-ov-file#pre-commit-hook
feat(actions): add `pre-commit` framework with `codespell` (#191)* feat(actions): add `pre-commit` framework with `codespell`Official -> "Git hook scripts are useful for identifying simple issues
feat(actions): add `pre-commit` framework with `codespell` (#191)* feat(actions): add `pre-commit` framework with `codespell`Official -> "Git hook scripts are useful for identifying simple issues before submission to code review. We run our hooks on every commit to automatically point out issues in code such as missing semicolons, trailing whitespace, and debug statements. By pointing these issues out before code review, this allows a code reviewer to focus on the architecture of a change while not wasting time with trivial style nitpicks."https://pre-commit.com/Using a `pre-commit` framework speeds up development as a lot of tests can be run on the local machine giving instant feedback. So we don't have to wait for the CI / GitHub actions to run to get feedback. The pre-commit automatically fixes some of the issues when you do git commit and if there are any issues the tests are marked as red failed. Then you will need to commit again so that all the tests pass green.When pre-commit runs with GitHub Actions on the GitHub website the hooks/tests either pass or fail.There are many more pre-commit checks listed here -> https://pre-commit.com/hooks.htmlLets get this PR merged and then I will look at adding more pre-commit tests ��This PR adds `codespell` to our pre-commit hooks.The words in `codespell.txt` are ignored and this file has basically been created by running:`codespell . | cut -f2 -d' ' | tr A-Z a-z | sort | uniq > codespell.txt`from the repo root.https://github.com/codespell-project/codespell`codespell` is one of the leading spell checkers on GitHub.Going forwards we will need to fix a lot of the misspelled words that are in `codespell.txt`* Exclude `extras` folder from spell check