Proposed changes

349 failed tests because of trailing whitespace left in the change. This was my mistake for trying to write the change entirely in-browser without cloning locally and running `pre-commit`, sorry.

Types of changes

What types of changes does your code introduce to this repository? Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Documentation Update

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] Lint and unit tests pass locally with my changes (if applicable)
[ ] I have run pre-commit (pre-commit in the repo)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Linked to the relevant github issue or github discussion

thinkst / opencanary

Trim Whitespace to Fix Pre-Commit Failure #350

Proposed changes

349 failed tests because of trailing whitespace left in the change. This was my mistake for trying to write the change entirely in-browser without cloning locally and running `pre-commit`, sorry.

Types of changes

Checklist

thinkst / opencanary

Trim Whitespace to Fix Pre-Commit Failure #350

Proposed changes

349 failed tests because of trailing whitespace left in the change. This was my mistake for trying to write the change entirely in-browser without cloning locally and running pre-commit, sorry.

Types of changes

Checklist

349 failed tests because of trailing whitespace left in the change. This was my mistake for trying to write the change entirely in-browser without cloning locally and running `pre-commit`, sorry.