Add pre-commit command

[blink1073]

• Refactor blackify into utility functions for prepping the repo and pushing work
• Add a "pre-commit" command target that runs pre-commit as a new commit and pushes.
• Test black and pre-commit in a PR
• Add docstrings
• Add documentation
• Make a run convenience function that prints the command
• Make keen optional so it isn't needed in non-prod apps (costs $300/mo on team account)
• Add contributor guide
• Add pre-commit config with flake8
• Add GitHub Actions testing (will require a B64KEY secret in this repo) - passing test

This is an on-demand alternative to the more disruptive "auto fixing pull requests" from https://pre-commit.ci/

[blink1073]

cc @choldgraf @consideRatio

[Carreau]

Let me know if you have access to heroku to debug if there are issues.

[blink1073]

On further thought, this won't work because if the hook changes anything it is considered a failure. Will need to do some more refactoring.

[blink1073]

@Carreau I don't think I have access to that heroku app, my account is under steven.silvester at gmail.com.

[blink1073]

Oh I see what you mean, I can deploy this myself.

[consideRatio]

Hi @blink1073!
Let me know if you want review or input with something specific @blink1073!

Note that I've not worked on this bot and hasn't used it besides learning that it can be used for backporting PRs by Min. Quickly glancing at the code I didn't see docstrings which otherwise could help me review something unknown by just knowing that the docstring declares the objective of a function.

I guess a technical review point could be that it would be good if you add docstrings to any function you add or re-purpose to help newcomers! :)

[blink1073]

Converting to draft while I test in blink1073#1. I'm putting this aside for the weekend.

[Carreau]

To deploy you can just merge this.
The heroku access is mostly for heroku logs --tail to help debugging if it fails somewhere.

[Carreau]

(and feel free to merge-try-revert to test if you need.)

[blink1073]

@Carreau I've finished. I ended up adding flake8 and GitHub Actions support.

[blink1073]

@consideRatio thanks for the feedback! I was pinging you and Chris as potential users of the new feature, no review required.

[Carreau]

Ok, let's just merge and see if things break. <3

[blink1073]

@Carreau can you please add me as a collaborator on the repo? I can add the env secret needed for the test

[Carreau]

Sorry, I thought you were.

…

On Wed, Mar 23, 2022 at 3:53 PM Steven Silvester ***@***.***> wrote: @Carreau <https://github.com/Carreau> can you please add me as a collaborator on the repo? I can add the env secret needed for the test — Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACR5T6AAWFZ2E4SEXGAUO3VBMV77ANCNFSM5RBNRBIQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Carreau]

Sorry, I thought you were.

I also invited you to the org in case you need even more permissions.

[blink1073]

I also invited you to the org in case you need even more permissions.

Cheers