*: add pre-commit

[hawkingrei]

What problem does this PR solve?

Issue Number: ref #43346

Problem Summary:

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

brew install pre-commit
pre-commit install

# give some commit and you will see the checking by pre-commit.

• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• tiancaiamao
• xhebox

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[xhebox]

I think you need to tell everyone that they need to install bazel now.

[hawkingrei]

I think you need to tell everyone that they need to install bazel now.

We can add a guide to check the environment and tell developers what to install while they are running the pre-commit.

BTW, pr-commit is not mandatory.

[tiancaiamao]

cat .git/hooks/pre-commit.sample

Should the .git/hooks directory be added to git? I'm not sure what is the best practice.

[hawkingrei]

cat .git/hooks/pre-commit.sample

Should the .git/hooks directory be added to git? I'm not sure what is the best practice.

I don't want to force every developer to use pre-commit. It is optional. If you want to use it, you can pre-commit install. If you want to remove, you only pre-commit uninstall. It is free for developers.

[hawkingrei]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 245fdf2

[tisonkun]

We can add a guide to check the environment and tell developers what to install while they are running the pre-commit.

@hawkingrei You can send a PR against https://github.com/pingcap/tidb-dev-guide and share the written page among the community. May or may not just file an issue right now :)

[hawkingrei]

We can add a guide to check the environment and tell developers what to install while they are running the pre-commit.

@hawkingrei You can send a PR against https://github.com/pingcap/tidb-dev-guide and share the written page among the community. May or may not just file an issue right now :)

OK, I will do it and this PR will not close this issue.