Add a pre-commit setup to the repository.

[vdemeester]

Changes

This will allow us to run some checks before committing. If direnv is enabled in the developer environment and pre-commit available, it will automatically install the hooks for the repository.

On top of #2175.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Run the code checkers with make check
• Regenerate the manpages, docs and go formatting with make generated
• Commit messages follow commit message best practices

See the contribution guide
for more details.

Release Notes

NONE

[chmouel]

I am good with the pre-commit part but still have concerns about .env file committed into the repo, the linked wiki page in the direnv wiki is not very clear of the advantages of doing this....

[chmouel]

Thanks for the update without dotenv,

/lgtm

[roman-kiselenko]

I guess the note about pre-commit installation should be in the https://github.com/tektoncd/cli/blob/main/DEVELOPMENT.md#requirements 🤔

[chmouel]

@roman-kiselenko that would be a great in this document have a brief explanation about what pre-commit does and how to install the hooks (basically run pre-commit binary at the root directory)

maybe mentions this as well in the pull request template with a link to that doc

[chmouel]

/lgtm

[piyush-garg]

/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: piyush-garg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [piyush-garg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment