blocks|key|4612622|text|如果您刚刚使用git+init，并且已经使用git+add+.或类似的工具添加了您的文件，并且已经添加了您的远程分支，那么您可能还没有在本地提交(git+commit+-m+'commit+message')任何内容来推送到远程...我刚犯了这个错误，这就是我的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4612623|entityMap^0|7|8|M|9|21|U|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

If you just used <code>git init</code> and have added your files with <code>git add .</code> or something similar and have added your remote branch it might be that you just haven't committed (<code>git commit -m 'commit message'</code>) anything locally to push to the remote... I just had this error and that was my issue.

blocks|key|4612652|text|如果您使用的是gerrit，这可能是由提交中不适当的Change-id引起的。尝试删除Change-Id，看看会发生什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4612653|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|$]]

If you are using gerrit, this could be caused by an inappropriate Change-id in the commit. Try deleting the Change-Id and see what happens.

blocks|key|4612684|text|记住在推送到Github+repo之前提交您的更改。这可能会解决您的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4612685|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|$]]

Remember to commit your changes before pushing to Github repo. This might fix your problem.

blocks|key|106129|text|我也有同样的问题。我遇到这个问题是因为我没有做任何提交，甚至是初始提交，而且我仍然在尝试推动。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106130|有一次我做了git+commit+-m+"your+msg"，然后一切都很好。|offset|length|style|CODE|106131|entityMap^0|0|6|O|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had same problem. I was getting this problem because i had not made any commit not even initial commit and still i was trying to push.

Once i did <code>git commit -m "your msg"</code> and then everything worked fine.

blocks|key|4612743|text|好吧，如果上面的答案都不起作用，如果你最近在ssh-add上搞砸了什么。试一试|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4612744|ssh-add+-D|code-block|syntax|javascript|4612745|entityMap^0|M|7|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Well if none of the above answers are working and if you have messed up something with <code>ssh-add</code> lately. Try

<pre><code>ssh-add -D
</code></pre>

blocks|key|106172|text|在推送之前，您必须添加并提交更改或执行git+push+-f+origin+master|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|106173|entityMap^0|J|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|$]]

before push you have to add and commit the changes or do <code>git push -f origin master</code>

blocks|key|106195|text|重命名您的分支，然后推送，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106196|git+branch+-m+new-name
git+push+-u+new-name|code-block|syntax|javascript|106197|这对我很有效。|106198|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|$]]

Rename your branch and then push, e.g.:

<pre><code>git branch -m new-name
git push -u new-name
</code></pre>

This worked for me.

blocks|key|4612820|text|不确定这是否适用，但我的修复方法是在git+init之后在本地提交一些东西。然后我使用--set-upstream推送到远程...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4612821|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|$]]

Not sure if this applies, but the fix for me was to commit something locally after git init. Then I pushed to remote using --set-upstream ...

blocks|key|106257|text|在推送之前未提交初始更改也会导致问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106258|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|$]]

Not commiting initial changes before pushing also causes the problem

blocks|key|4612881|text|创建一个为我解决的新分支：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4612882|git+checkout+-b+<nameOfNewBranch>|code-block|syntax|javascript|4612883|正如预期的那样，不需要合并，因为以前的分支完全包含在新的分支中。|4612884|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|$]]

Creating a new branch solved for me:

<pre><code>git checkout -b &lt;nameOfNewBranch&gt;
</code></pre>

As expected no need to merge since previous branch was fully contained in the new one.

blocks|key|4612922|text|如果您尝试使用现有的GitHub存储库初始化目录，则应确保您正在提交更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4612923|尝试创建文件：|4612924|touch+initial
git+add+initial
git+commit+-m+"initial+commit"
git+push+-u+origin+master|code-block|syntax|javascript|4612925|这将放置一个名为initial的文件，您可以稍后删除该文件。|4612926|希望这个答案能有所帮助！祝你好运！|4612927|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

If you are attempting to initialize a directory with an existing GitHub repository, you should ensure you are committing changes.

Try creating a file:

<pre><code>touch initial
git add initial
git commit -m "initial commit"
git push -u origin master
</code></pre>

That will place a file named initial that you can delete later.

Hope this answer helps! Goodluck!

blocks|key|4612940|text|git+push+origin+{your_local_branch}:{your_remote_branch}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|4612941|如果您的本地分支和远程分支共享相同的名称，那么您可以省略本地分支的名称，只使用git+push+{your_remote_branch}。否则它将抛出此错误。|unstyled|offset|length|style|CODE|4612942|entityMap^0|0|13|T|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|N|8|@$G|O|H|P|I|J]]|9|@]|A|$]]|$1|K|3|-4|5|F|7|Q|8|@]|9|@]|A|$]]]|L|$]]

<pre><code>git push origin {your_local_branch}:{your_remote_branch}
</code></pre>

If your local branch and remote branch share the same name, then can you omit your local branch name, just use <code>git push {your_remote_branch}</code>. Otherwise it will throw this error.

blocks|key|4612968|text|对于资源树用户|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4612969|首先进行初始提交或确保没有未提交的更改，然后在sourcetree的一侧有一个"REMOTES"，右键单击它，然后单击“Push+to+origin”。这就对了。|4612970|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

For sourcetree users

First do an initial commit or make sure you have no uncommited changes, then at the side of sourcetree there is a "REMOTES", right-click on it, and then click 'Push to origin'. There you go.

blocks|key|4613050|text|当您没有任何文件时，可能会发生这种情况。尝试创建一个文本文件，然后执行以下命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4613051|git+add+.
git+commit+-m+"first+commit"
git+push+--set-upstream+origin+master|code-block|syntax|javascript|4613052|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

It may happen when you don't have any files.
Try to create a text file then follow the following commands

<pre><code>git add .
git commit -m "first commit"
git push --set-upstream origin master
</code></pre>

blocks|key|4613100|text|这发生在我身上，因为我有一个与分支相同的标签，并且我试图将分支推送到远程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4613101|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 happens to me as I had a tag with the same as the branch and I tried to push the branch to remote.

blocks|key|4613115|text|对我来说，问题是，我没有在提交之前添加文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4613116|git+add+.|offset|length|style|CODE|4613117|git+commit+-m+"your+msg"|4613118|entityMap^0|0|0|9|0|0|O|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

For me the Problem was, I did not add the files before the commit.

<code>git add .</code>

<code>git commit -m "your msg"</code>

blocks|key|4613147|text|在我的例子中，问题是(奇怪的)没有叫做master的分支。我从Github那里拿到了存储库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4613148|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 the problem was that (strangely) there was no branch called master. I took the repository from Github.

blocks|key|106558|text|我正在推送现有的拼写错误的“信封”分支，而我还没有结账，相反，我想推送一个叫做“信封”的分支。因此，分支必须存在/签出在本地工作副本，以推送当然，因此错误，不会犯打字错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106559|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 was pushing existing typo 'evelop' branch which I did not have checkout yet, and instead, I wanted to push a branch called 'envelope'. So the branch must be existing/checkout out at local working copy in order to push of course, therefore that error, not to make a typo.

blocks|key|106569|text|执行这些操作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106570|git+rm+--cached+*
git+add+.
git+commit+-m"upload"
git+push+--set-upstream+origin+master|code-block|syntax|javascript|106571|祝你编码愉快！|106572|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|$]]

do these

<pre><code>git rm --cached *
git add .
git commit -m"upload"
git push --set-upstream origin master
</code></pre>

Happy coding!

blocks|key|106606|text|不幸的是，我不能用另一个解决方案解决这个问题，但我的问题是我想推送的分支名称不被远程接受。我将其更改为正确的格式并接受。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106607|它是test/testing_routes，需要将其更改为远程不允许的testing_route。|offset|length|style|CODE|106608|您应该确保分支名称格式正确。|106609|entityMap^0|0|2|J|Z|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

Unfortunately, I could not solve the problem with the other solution but my problem was that the branch name I want to push was not accepted by remote. I change it to the correct format and accepted.

it was <code>test/testing_routes</code> and needed to change it to <code>testing_route</code> which the <code>/</code> is not allowed by remote. 

You should ensure that the branch name format is correct.

blocks|key|106650|text|在我的例子中，分支名称前缀已经存在于远程，所以基本上，如果你有一个分支名称'fix‘，你不能推送另一个名称为'fix/new_+branch+_+name’的分支，重命名分支解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106651|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 branch name prefix was already present at remote so basically if you have a branch name 'fix' you cannot push another branch with name 'fix/new_branch_name', renaming branch solved my problem.

blocks|key|4613276|text|最好使用rm+-rf+.git/hooks，然后尝试git推送|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4613277|entityMap^0|4|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|$]]

Best use <code>rm -rf .git/hooks</code> and then try git push

blocks|key|106685|text|试试这个git命令，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106686|git+push+origin+master+–f
git+push+origin+master+--force|code-block|syntax|javascript|106687|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Try this git command,

<pre><code>git push origin master –f
git push origin master --force
</code></pre>

blocks|key|106703|text|我遵循了以下步骤，它对我来说是有效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106704|+rm+-rf+.git
+git+init
+git+add+.
+git+commit+-m"first+message"
+git+remote+add+origin+"LINK"
+git+push+-u+origin+master|code-block|syntax|javascript|106705|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I followed the following steps and it worked for me.

<pre><code> rm -rf .git
 git init
 git add .
 git commit -m"first message"
 git remote add origin "LINK"
 git push -u origin master
</code></pre>

blocks|key|106726|text|GitHub将master改为main的事实让我遇到了这个问题。所以从现在开始，推送到原点的解决方案是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106727|git+push+-u+origin+main|code-block|syntax|javascript|106728|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The fact that GitHub changed master to main made me encounter this issue. So from now on, the solution to push to origin is:
<pre><code>git push -u origin main
</code></pre>

blocks|key|106767|text|因为也许没有什么可以推动的(真的，没有东西可以推动)。像这样做|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106768|git+remote+add+origin+https://github.com/donhuvy/accounting133.git
git+remote+-v
git+add+.
git+commit+-m"upload"
git+push+--set-upstream+origin+master|code-block|syntax|javascript|106769|在您的案例中更改远程存储库url。命令git+remote+-v你可以跳过，只是为了检查。|offset|length|style|CODE|106770|entityMap^0|0|0|J|D|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|$]]

Because maybe have nothing to push (really, no thing to push). Do like this
<pre><code>git remote add origin https://github.com/donhuvy/accounting133.git
git remote -v
git add .
git commit -m&quot;upload&quot;
git push --set-upstream origin master
</code></pre>
Change the remote repository url in your case. Command <code>git remote -v</code> you can skip, just for checking.

blocks|key|4613419|text|这可能不是一个常见的问题，但它发生在我身上，所以我将它作为注释添加到这里，以防其他人犯下我所犯的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4613420|我创建了一个自定义的预推文件，但我忘了以exit+0结尾|offset|length|style|CODE|4613421|这导致我得到这个“无法推送一些引用”的错误。我将exit+0添加到我的预推钩子的末尾，当然，它现在工作得很好。|4613422|entityMap^0|0|K|6|0|O|6|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

This is probably not a common problem, but it happened to me, so I'll add it as a comment here in case someone else makes the mistake I did.
I created a custom pre-push file, and I forgot to end it with <code>exit 0</code>
That caused me to get this &quot;failed to push some refs&quot; error. I added <code>exit 0</code> to the end of my pre-push hook and, of course, it works fine now.

blocks|key|106869|text|使用Azure+DevOps中的Git+repo，问题是分支策略要求对分支的所有更改都必须通过拉取请求进行。尝试将更改直接推送到分支时生成错误“无法将某些引用推送到...”。我创建了一个公关分支，并且推送没有问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106870|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|$]]

Using a Git repo in Azure DevOps, the problem was a branch policy requiring that all changes to the branch must be made via pull request. Trying to push changes directly to the branch generated the error &quot;failed to push some refs to ...&quot;. I created a PR-branch and pushed without problem.

blocks|key|106912|text|在我的例子中，我拼写错了分支的名称。在本地我做了一些类似的事情：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|106913|git+push+--set-upstream+origin+feture/my-feature|offset|length|style|CODE|106914|我的分支名称在feature中缺少a。我将其更正为：|106915|git+push+--set-upstream+origin+feature/my-feature|106916|一切都运行得很好。|106917|entityMap^0|0|0|1C|0|7|7|H|1|0|0|1D|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|O|$]]

In my case I misspelled the name of the branch. Locally I did something like:
<code>git push --set-upstream origin feture/my-feature</code>
where my branch name was missing the <code>a</code> in <code>feature</code>. I corrected it to:
<code>git push --set-upstream origin feature/my-feature</code>
And everything worked fine.

blocks|key|4613579|text|我面对这个问题，但两天后我得到了一个解决方案。如果是第一次在GitHub页面上部署站点，只需运行这两个命令即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4613580|git+commit+-m+"initial+commit"
git+push+origin+%2BHEAD|code-block|syntax|javascript|4613581|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I faced this issue but after 2 days I got a solution.
Just run these two commands if you are deploying your site on GitHub pages first time.
<pre><code>git commit -m &quot;initial commit&quot;
git push origin +HEAD
</code></pre>

blocks|key|4613637|text|在我的例子中，git+pre-push钩子有一个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4613638|运行git+push+--verbose查看是否有任何错误。|4613639|仔细检查.git/hooks目录中的git-hook，或者临时将它们移到另一个位置，看看之后是否一切正常。|4613640|entityMap^0|B|8|0|2|I|0|4|A|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

In my case there was a problem with a git <code>pre-push</code> hook.
Run <code>git push --verbose</code> to see if there are any errors.
Double check your git-hooks in the directory <code>.git/hooks</code> or move them temporarily to another place and see if everything works after that.

blocks|key|4613660|text|Github将默认分支名称从master更改为main。因此，如果您最近创建了存储库，请尝试推送main分支|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4613661|git+push+origin+main|code-block|syntax|javascript|4613662|这是初学者可能会犯的常见错误。|4613663|Github+Article|4613664|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/github/renaming^0|E|6|N|4|1C|4|0|0|0|0|E|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|O|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

Github changed the default branch name from <code>master</code> to <code>main</code>.
So if you created the repo recently, try pushing <code>main</code> branch
<pre><code>git push origin main
</code></pre>
This is a common mistake, beginners can make.
<a href="https://github.com/github/renaming" rel="nofollow noreferrer">Github Article</a>

blocks|key|4613690|text|在我们的例子中，重新尝试推送解决了问题。可能是网络速度慢导致了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4613691|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 our case, retrying to push solved the problem. Probably a network slowness caused the issue.

blocks|key|4613714|text|在我的例子中，我错过了修改，我只需要运行git+commit+--amend然后推送。它修复了这个问题。它可能会对以前提交过代码的人有所帮助。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4613715|entityMap^0|K|I|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, I missed amending, I just needed to run <code>git commit --amend</code> and then push. It fixed the issue. It might help someone who has previously committed code.

blocks|key|107174|text|如果您创建了一个空的存储库并忘记使用，您也会收到此错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|107175|git+init|code-block|syntax|javascript|107176|在推送您的第一个提交之前，首先。|107177|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|$]]

You will also get this error if you created an empty repo and forgot to use
<pre><code>git init
</code></pre>
first before pushing your first commit.

blocks|key|107220|text|我尝试了'git+push+working+main‘，然后得到了消息，然后我尝试了单独'git+push’，但不起作用。我检查了我是否已经承诺确认(是)。我又试了一次“拉”和“推”，没有。在开始一些特技之前，我只是关闭并打开了一个新的终端，然后再次“推”，它起作用了:p|type|unstyled|depth|inlineStyleRanges|entityRanges|data|107221|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 tried the 'git push origin main' then got the message, then I tried 'git push' alone, not working. I checked if I had committed to be sure (yes). I tried the 'pull' then 'push' again, nope. and before to start some stunts I just closed and opened a new terminal and then 'push' again and it worked :p

blocks|key|4613809|text|由于最近的“在GitHub中用main替换master”操作，如果您执行git+show-ref，您可能会注意到有一个refs/heads/main。因此，以下命令可能会从|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4613810|git+push+heroku+master|4613811|至|4613812|git+push+heroku+main|4613813|这会解决你的问题|4613814|entityMap^0|10|C|0|0|M|0|0|0|K|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|Z|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|O|$]]

Due to the recent &quot;Replacing master with main in GitHub&quot; action, you may notice that there is a refs/heads/main if you do <code>git show-ref</code>. As a result, the following command may change from
<code>git push heroku master</code>
to
<code>git push heroku main</code>
That will solve your issue

blocks|key|107278|text|检查您的互联网是否工作正常，是否有良好的速度。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|107279|我试着用我的4G手机热点推送，但收到这个错误将近10分钟。|107280|附注:在印度，我们有4G网络的3G速度，所以在做一些花哨的事情之前，先看看是否有合理的速度:)|107281|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|$]]

Check if your internet is working fine and has got good speed.
I was trying to push with my 4G mobile hotspot and getting this error for nearly 10 minutes.
P.S. Here in India, we get 3G speed for 4G network, so before doing something fancy; just see if there is reasonable speed available :)

blocks|key|107300|text|对于我来说，几个代码的组合对我来说是有效的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|107301|$+git+reset+
$+git+remote+-v
$+git+pull+--rebase
$+git+init
$+git+add+-A
$+git+commit+-m+"Add+your+commit"
$+git+branch+-M+main
$+git+push+origin+main+--force|code-block|syntax|javascript|107302|他们必须小心，如果他们有一个自述文件，git重置会删除他们。|107303|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|$]]

It has worked for me with this combination of several codes:
<pre><code>$ git reset 
$ git remote -v
$ git pull --rebase
$ git init
$ git add -A
$ git commit -m &quot;Add your commit&quot;
$ git branch -M main
$ git push origin main --force
</code></pre>
They must be careful, if they have a Readme file, the git reset deletes them.

blocks|key|4613891|text|如果您使用的是git+push+origin+master，请将其更改为git+push+origin+main，反之亦然|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4613892|entityMap^0|7|M|10|K|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

if you were using <code>git push origin master</code>, change it to <code>git push origin main</code> and vice versa

For some reason, I can't push now, whereas I could do it yesterday.
Maybe I messed up with configs or something.

This is what happens:

When I use the git push origin master

<img src="https://i.stack.imgur.com/hOuSj.png" alt="gitbashscr">

What my working directory and remote repository looks like:

<img src="https://i.stack.imgur.com/Sz17u.png" alt="Screenshot of Windows file folder with these directories: .git, css, js. And these files: index.php, readme, setsu.php. The word &quot;local&quot; with an arrow points to the css-folder. Below, screenshot with heading &quot;github&quot;, and a css-folder and index.php-file">

git error: failed to push some refs to remote

DevOps

GitHub

由于某种原因，我现在不能推，而我昨天可以推。也许我搞砸了配置之类的东西。这就是发生的事情：当我使用git推送原始母版时​​我的工作目录和远程存储库是什么样子：​​

问git错误:无法将某些ref推送到远程
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git错误:无法将某些ref推送到远程EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git错误:无法将某些ref推送到远程
EN