Adding a Base Configuration for Pre-commit Hooks #49
Description
Why
pre-commit along with its pre-defined hooks, are helpful to perform certain operations before each commit, which help to catch the issues early and avoid wasting CI time. It includes (but not limited to) the following steps:
- Trimming trailing whitespace
- Ensuring files end with a single newline
- Preventing large files from being committed
- Verifying the syntax of YAML files
- Detecting and blocking hardcoded secrets
- And more...
By adding some default pre-config hook configurations to the git template, it can be applied to future projects
Who Benefits?
- The development team, who doesn't need to waste time on fixing those issues on the PRs
- The CI cost