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/08/24/%E5%A6%82%E4%BD%95%E7%BB%99%E6%9F%90%E4%B8%80%E7%B1%BB%E9%A1%B9%E7%9B%AE%E7%BB%9F%E4%B8%80%E8%AE%BE%E7%BD%AE%E7%94%A8%E6%88%B7%E5%90%8D%E5%92%8C%E9%82%AE%E7%AE%B1/index.html
在浏览公司项目的时候,发现总有提交记录使用的是用户名和邮箱根本看不出来是哪路神仙提交了代码,这种情况最好的方案当然是在服务器上设置 git hook 检查,统一使用真实用户名及公司邮箱,对于不满足条件的一律拒绝 push 代码。 然而这个时候如果用户一个不上心在本地使用了不符合规范的用户名邮箱 commit 代码,则需要用户修改历史提交信息,变更用户名邮箱重新 push,说实在的一般 git 用户
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://leemotive.github.io/2022/08/24/%E5%A6%82%E4%BD%95%E7%BB%99%E6%9F%90%E4%B8%80%E7%B1%BB%E9%A1%B9%E7%9B%AE%E7%BB%9F%E4%B8%80%E8%AE%BE%E7%BD%AE%E7%94%A8%E6%88%B7%E5%90%8D%E5%92%8C%E9%82%AE%E7%AE%B1/index.html
在浏览公司项目的时候,发现总有提交记录使用的是用户名和邮箱根本看不出来是哪路神仙提交了代码,这种情况最好的方案当然是在服务器上设置 git hook 检查,统一使用真实用户名及公司邮箱,对于不满足条件的一律拒绝 push 代码。 然而这个时候如果用户一个不上心在本地使用了不符合规范的用户名邮箱 commit 代码,则需要用户修改历史提交信息,变更用户名邮箱重新 push,说实在的一般 git 用户
The text was updated successfully, but these errors were encountered: