blocks|key|741214|text|你应该问问在git@mycogit/cit_pplus.git维护回购的人。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|741215|您的提交被该repo的pre-receive+hook拒绝(这是一个用户可配置的脚本，用于分析传入的提交并决定它们是否足够好，可以被接受到repo中)。|741216|让那个人更新钩子也是一个好主意，这样它就会打印出拒绝的原因。|741217|如果维护者就是您自己，那么看起来您在服务器端的设置就有问题。届时请分享更多信息。|741218|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks#Server-Side-Hooks^0|6|P|0|B|B|B|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|13|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

You should ask whoever maintains the repo at <code>git@mycogit/cit_pplus.git</code>.

Your commits were rejected by the <a href="http://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks#Server-Side-Hooks" rel="noreferrer"><code>pre-receive</code> hook</a> of that repo (that's a user-configurable script that is intended to analyze incoming commits and decide if they are good enough to be accepted into the repo). 

It is also a good idea to ask that person to update the hook, so it would print the reasons for the rejection.

If the maintainer is you yourself, then it looks like you've got a problem with your setup on the server-side. Please share more information then.

blocks|key|741320|text|我敢打赌，您正在尝试非快进推送，但钩子会阻止它。如果是这种情况，只需在推送之前运行git+pull+--rebase，以根据最新的代码库重新设置本地更改的基础。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|741321|entityMap^0|15|H|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I'd bet that you are trying a non-fast-forward push and the hook blocks it. If that's the case, simply run <code>git pull --rebase</code> before pushing to rebase your local changes on the newest codebase.

blocks|key|741494|text|文件大小很重要。单个文件的大小限制为~120MB。在我的例子中，使用Visual+Studio的.gitignore列出了该文件，但该文件仍被提交。使用git+cli时，我们可以获得有关错误的更多详细信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|741495|预接收钩子被拒绝是大文件的结果。基本上验证了推送。|741496|为了解决这个问题，我使用以下命令删除了最后一个提交：|741497|git+reset+--soft+HEAD~1|code-block|syntax|javascript|741498|然后，我从提交中排除了该文件。|741499|注意:使用HEAD~N返回到之前的N次提交。(例如，3、4)始终使用--软开关来维护文件夹中的更改|741500|希望能有所帮助。|741501|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

File size is important. There is a limit of ~120MB for a single file. In my case, .gitignore using Visual Studio had the file listed, but the file was still committed. When using the git cli, we can get more detail information about the error.

pre-receive hook declined was as a result of the big file. Basically validating the push.

To resolve it, I removed the last commit using: 

<pre><code>git reset --soft HEAD~1
</code></pre>

I then excluded the file from the commit.

Note: 
Use HEAD~N to go back to N number of previous commits. (i.e. 3, 4)
Always use the --soft switch to maintain changes in the folder

hope it helps.

blocks|key|525116|text|在我的例子中，我收到这条消息是因为分支在GitLab中被标记为“Protected”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|525117|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case I got this message because the branch was marked as 'Protected' in GitLab.

blocks|key|524889|text|这可能是因为您没有将提交推送到master等分支的访问权限。您可以要求维护者给您推送提交的权限。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|524890|entityMap^0|F|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

This may be because you didn't have the access right to push a commit to a branch such as <code>master</code>. You can ask the maintainer to give you the right to push commits.

blocks|key|525050|text|当GitLab服务器正在进行一些更改时，我收到了这条消息。第二天，推送工作得很好。无论如何，正如其他人指出的那样，请与您的维护者确认一下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|525051|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this message when the GitLab server was undergoing some changes. The next day pushing worked fine. Anyways, as others pointed out, check with your maintainer to be sure.

blocks|key|742228|text|有时，因为您正在推送的分支已经受到保护，所以您可以要求存储库的维护人员更改保护状态。在git-lab中，您可以在|type|unstyled|depth|inlineStyleRanges|entityRanges|data|742229|Settings+>+Repository+>+Protected+Branches+.|code-block|syntax|javascript|742230|:)|742231|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

in sometimes, because the branch you are pushing has been protected, so you can ask the repository's maintainers to change the protecting status. in git-lab , you can find it in
<pre><code>Settings &gt; Repository &gt; Protected Branches .
</code></pre>
:)

blocks|key|741804|text|我遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|741805|对我来说，解决这个问题的方法是切换到另一个分支，然后再回到原来的分支。|741806|不确定下划线的原因是什么，但这解决了它。|741807|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I encountered this same issue. 
What solved it for me was to switch to another branch and then back to the original one.

Not sure what the underline cause was, but this fixed it.

blocks|key|524930|text|当我尝试合并文件大小超过远程存储库允许的大小的更改时(在我的例子中是GitHub)，我遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|524931|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this issue when trying to merge changes with file size greater than what remote repository allowed (in my case it was GitHub)

blocks|key|742542|text|在我的案例中，问题是Rewriting+branch+history+is+not+allowed限制。转到Repository+settings+->+Branch+Permissions编辑所选分支的权限，然后选中Allow+rewriting+branch+history|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|742543|​|742544|📷|atomic|742545|742546|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/3e86a3f84b43e50a52325bef581acbce.png|imageAlt^0|A|13|1I|15|31|U|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|K|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

On my case, the problem was <code>Rewriting branch history is not allowed</code> restriction.
Go to <code>Repository settings -&gt; Branch Permissions</code> edit the selected branch's permissions, and check <code>Allow rewriting branch history</code>
<img src="https://i.stack.imgur.com/Az07W.png" alt="Allow rewriting branch history" />

blocks|key|742062|text|我遇到了同样的错误，在检查时，我拥有开发人员访问权限，无法发布新的分支。添加更高的访问权限解决了此问题。(Gitlab)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|742063|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I faced the same error, upon checking I had a developer access and couldn't publish a new branch. Adding higher access rights resolved this issue.(Gitlab)

blocks|key|525588|text|我在GitHub+gist中得到了这个错误。我正在尝试对子目录中的文件推送提交。原来的gist只能在根目录下有文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|525589|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this error with GitHub gist.
I was trying to push a commit with files in sub-directories.
Turned out gist can only have files in root directory.

blocks|key|525704|text|删除受保护分支选项或允许其他角色，如开发人员或管理员，以允许这些遇到此错误的用户执行合并和推送。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|525705|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Remove the protected branch option or allow additional roles like developers or admins to allow these users experiencing this error to do merges and push.

blocks|key|525218|text|在我的例子中，我们有用于提交消息的钩子，我们的服务器脚本接受提交，如果它们具有提交消息"<JIRA+ID><Message>"的特殊格式。如果相应的Jira票证不存在或在提交消息中有一些特殊符号，它(挂钩)将拒绝提交。当我在提交消息中添加/、[，>等时，我遇到了这个错误，删除它们可以很好地工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|525219|entityMap^0|17|K|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

In my case, we have hooks for commit messages, our server script accepts commits if they have the special format for commit message<code>"&lt;JIRA ID&gt;&lt;Message&gt;"</code>. It(hook) declines commit if respective Jira ticket does not exist or there are some special symbols in the commit message. I face this error when I add /, [, > etc. in a commit message, removing those works fine.

blocks|key|525250|text|这实际上是在BitBucket中的服务器端启用YACC时发生的。对于要在提交消息中提及的JIRA问题名称，启用了YACC。因此，当您提交任何东西时，至少要将您的JIRA编号保留在提交消息中，然后您还可以添加自己的消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|525251|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This is actually happens when YACC is enabled at server side in BitBucket. YACC is enable for JIRA issue names to be mentioned in the commit message. So whenever you commit anything atleast keep your JIRA number into the commit message and then additionally you can add your own message.

blocks|key|741867|text|对于我来说，远程git服务器上的授权解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|741868|📷|atomic|offset|length|741869|​|741870|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/cd9ad3cdb2f9cb80a579853bbd8027b3.png|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

For me Authorization on remote git server solve the problem.
<a href="https://i.stack.imgur.com/Bj099.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Bj099.png" alt="enter image description here"></a>

blocks|key|525944|text|在我的例子中，我得到这个错误是因为已经存在具有相同名称的分支。从git服务器上删除此分支可以修复此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|525945|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case I got this error because a branch with the same name already existed. Deleting this branch off of the git server will fix this.

blocks|key|741657|text|当我试图推送到dokku实例时，我得到了这个。原来我服务器上的磁盘已经满了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|741658|Ran：du+-f|offset|length|style|CODE|741659|结果是：|741660|Filesystem++++++Size++Used+Avail+Use%25+Mounted+on
udev++++++++++++476M+++++0++476M+++0%25+/dev
tmpfs+++++++++++100M++4.4M+++95M+++5%25+/run
/dev/xvda1++++++7.8G++7.4G++8.9M+100%25+/|code-block|syntax|javascript|741661|entityMap^0|0|4|5|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|V|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I got this when trying to push to a dokku instance. Turns out the disk was full on my server.

Ran:
<code>du -f</code> 

And result was:

<pre><code>Filesystem Size Used Avail Use% Mounted on
udev 476M 0 476M 0% /dev
tmpfs 100M 4.4M 95M 5% /run
/dev/xvda1 7.8G 7.4G 8.9M 100% /
</code></pre>

blocks|key|525434|text|在我的例子中，这是因为我不小心在未提交的推送中添加了一个巨大的文件，无论我之后做了什么pull、reset或rm操作，我都无法摆脱它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|525435|我的解决方案是重命名当前目录，将目录重新克隆到本地目录，并手动将更改反映到重新克隆的本地目录中。|525436|这听起来不是很好，但很有效。|525437|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In my case, it's because I accidentally added a giant file to my uncommitted push and I could not get rid of it no matter whatever pull or reset or rm I did after.

my dirty solution but workable solution is to rename the current directory, re-clone the directory to local and reflect the changes manually to the recloned local directory...

It does not sound good but works...

blocks|key|742015|text|对我来说，错误是项目没有创建任何分支，而我的角色是开发人员，所以我不能创建任何分支，请求他们现在就给我相关的权限和一切！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|742016|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The error for me was that the project did not have any branches created, and my role was developer, so I could not create any branch, request that they give me the pertinent permissions and everything in order now!

blocks|key|525662|text|您的遥控器尚不存在默认分支(例如master)。因此，你首先需要在git远程服务器中创建master分支(例如，创建一个默认的README.md文件)，然后尝试使用以下命令push所有现有的本地分支：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|525663|git+push+-u+origin+--all|code-block|syntax|javascript|525664|entityMap^0|G|6|18|6|1R|9|2E|4|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|L|$]]

A default branch (e.g. <code>master</code>) does not yet exist for your remote. So you first need to create <code>master</code> branch in the git remote server (e.g. creating a default <code>README.md</code> file) then try to <code>push</code> all your existing local branches using this command:

<pre><code>git push -u origin --all
</code></pre>

blocks|key|742290|text|我在尝试删除远程分支时收到此消息(git+push+origin+--delete+branch-name)。问题是分支在bitbucket中被标记为不可删除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|742291|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this message while trying to delete a remote branch (git push origin --delete [branch-name]). The problem was that the branch was marked un-deletable in bitbucket.

blocks|key|525840|text|我有权限问题，在得到正确的权限后，我可以推送内容。我正在将一个现有的项目推送到一个新的git+repo中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|525841|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had permissions issue, after given the right permissions i was able to push the contents. I was pushing a existing project into a new git repo.

blocks|key|742371|text|你应该看看日志。我刚刚遇到了同样的错误，并从日志中意识到这是因为我有一个yarn.lock和包-lock.json|type|unstyled|depth|inlineStyleRanges|entityRanges|data|742372|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You should look at the logs. I just ran into the same error and realized from the logs it was because I had a yarn.lock and package-lock.json

blocks|key|525982|text|您的提交与存储库维护者的规则不兼容，您只需执行git+reset+--hard+HEAD+~+1命令即可删除最后一次提交。在那之后，根据维护者的规则，一切都是可以的|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|525983|entityMap^0|N|P|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Your commit is not compatible with the repository maintainer's rules, you just need to <code>git reset --hard HEAD ~ 1</code> in order to delete the last commit. After that commitment according to the maintainer's rules is ok

blocks|key|742610|text|我通过重新生成SSH密钥并将其添加到GitHub帐户解决了此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|742611|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I resolved this issue with regenerating SSH key and adding it to the GitHub account.

blocks|key|526171|text|我也遇到过类似的问题，它是由bcrypt+npm包引起的。我卸载了bcrypt，转而安装了bcryptjs。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|526172|npm+install+--save+bcryptjs+&&+npm+uninstall+--save+bcrypt|code-block|syntax|javascript|526173|这是完全相同的API。除了需要将require调用更改为require("bcryptjs");之外，app.js内部的所有代码都保持不变|offset|length|style|CODE|526174|entityMap^0|0|0|S|K|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I had a similar issue and it was caused by bcrypt npm package. I uninstalled bcrypt and instead installed bcryptjs.
<pre><code>npm install --save bcryptjs &amp;&amp; npm uninstall --save bcrypt
</code></pre>
It's the exact same API. All the code inside app.js remains same except the require call need to be changed to <code>require(&quot;bcryptjs&quot;);</code>

When I try and push a change I've commited, I get the following error ...

<pre><code>git.exe push -v --progress "origin" iteration1:iteration1

remote: *********************************************************************
To ssh://git@mycogit/cit_pplus.git
! [remote rejected] iteration1 -&gt; iteration1 (pre-receive hook declined)
error: failed to push some refs to 'ssh://git@mycogit/cit_pplus.git'
</code></pre>

What's going on?

Git error when trying to push -- pre-receive hook declined

当我尝试推送我提交的更改时，我得到以下错误...git.exe push -v --progress  "origin" iteration1:iteration1remote: *********************************************************************To ssh://git@mycogit/cit_pplus.git! [remo

问尝试推送时出现Git错误--预接收钩子被拒绝
EN

回答 27

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试推送时出现Git错误--预接收钩子被拒绝EN

回答 27

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试推送时出现Git错误--预接收钩子被拒绝
EN