We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://leemotive.github.io/2022/12/11/merge%E5%90%8E%E7%9A%84commit%E8%B7%B3%E8%BF%87%E6%A3%80%E6%9F%A5/index.html
项目代码风格,一般会在 git 的 pre-commit 这个 hook 中进行代码风格的校验,如果校验失败将阻止本次代码的提交。需要将不符合规范的所有问题代码全部修复才能重新提交成功。 项目概况在我的项目里,使用的是 eslint, prettier, lint-staged来完成这些格式化及规范检查的,这也应该是前端项目最常用的两个工具了吧 由于这些校验工具是在项目中期引入的,代码需要修复的问
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://leemotive.github.io/2022/12/11/merge%E5%90%8E%E7%9A%84commit%E8%B7%B3%E8%BF%87%E6%A3%80%E6%9F%A5/index.html
项目代码风格,一般会在 git 的 pre-commit 这个 hook 中进行代码风格的校验,如果校验失败将阻止本次代码的提交。需要将不符合规范的所有问题代码全部修复才能重新提交成功。 项目概况在我的项目里,使用的是 eslint, prettier, lint-staged来完成这些格式化及规范检查的,这也应该是前端项目最常用的两个工具了吧 由于这些校验工具是在项目中期引入的,代码需要修复的问
The text was updated successfully, but these errors were encountered: