github企业错误推动本地货币
在推动从本地到GitHub Enterprise的更改时遇到以下错误。
remote: Resolving deltas: 100% (10/10), completed with 10 local objects.
remote: Jira-validation-hook.sh: execution exceeded 5s timeout
To https://github.abc.com/PLK/projectabc.git
error: failed to push some refs to 'https://github.abc.com/PLK/projectabc.git'
! refs/heads/SP-121:refs/heads/SP-121 [remote rejected] (pre-receive hook declined)
Done
Getting the following error while pushing the changes from local to github enterprise.
remote: Resolving deltas: 100% (10/10), completed with 10 local objects.
remote: Jira-validation-hook.sh: execution exceeded 5s timeout
To https://github.abc.com/PLK/projectabc.git
error: failed to push some refs to 'https://github.abc.com/PLK/projectabc.git'
! refs/heads/SP-121:refs/heads/SP-121 [remote rejected] (pre-receive hook declined)
Done
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在GitHub Enterprise上，管理员可能会添加一个预先接收的挂钩，以控制是否允许数据。但是，此钩必须在5秒内完成。
在您的服务器的情况下，挂钩花费的时间比预期的时间更长，因此操作失败了，推动被拒绝。如果服务器恰好恰好被超载，您可以再次尝试推动，但是通常，这是您的GitHub Enterprise Administration人才可以修复的东西。他们需要修复脚本以减少推动时花费更少的时间，因此您应该与他们联系并要求他们这样做。
On GitHub Enterprise, it's possible for the administrators to add a pre-receive hook that controls whether data should be allowed or not. This hook, however, must complete within 5 seconds.
In your server's case, the hook took longer than it was supposed to, and therefore the operation failed, and the push was rejected. You can try your push again in case the server just happened to be overloaded, but in general, this is something only your GitHub Enterprise administrator can fix. They'd need to fix their script to take less time when pushes occur, so you should contact them and ask them to do so.