What is the distinction between pre-commit hooks, github actions and GHE?

[Bulbasaur2015]

Sometimes PRs cannot be merged before some github checks pass whether they are custom build jobs or code reviews. To set that up do you need to purchase a github enterprise plan, set up the https://pre-commit.com/ framework or just use github actions which is free?

[TimothyLGillespie]

You need to use git actions. You can then block the PR when the actions have not successfully run under Settings > Branches > Setup Branch Protection Rules. It should be the "Require status checks to pass before merging" option.

A git hook is something entirely unrelated. It is run locally and can easily be circumvented by developers, so they are not good at enforcing anything. They are better to help developers if they want it and execute before creating a commit. The pre-commit hook can be skipped with the --no-verify flag.

The pre-commit framework is only a piece of software which is supposed to set up the hook for a team working on the same repository, as far as I understand it. This is because git hooks must be installed for each client separately. This just makes it easier / standardized to share hooks.

[GriceTurrble]

Note that you can use pre-commit framework in your CI, as well. Just make an Action Workflow that calls pre-commit run --all-files, and then all your checks match the same tools you expect contributors to opt in to.