Visual studio 2019 "Error encountered while pushing to the remote repository: Failed to push to the remote repository..."

Question

In Visual Studio 2019 I have "Unpushed Commits" as seen below:

When I try to push them I get the error and this is what it looks like on the GUI:

note: the yellow label with "Failed to push..." is not clickable.

The Output from Source Control - Git is as follows:

The output window doesn't show me any useful details. Am I looking in the wrong place? Is there a better place to see the actual error?

The answer in this case is that the policy on the branch 'develop' does not allow direct pushes. I was kinda hoping that the error in the output would state something like 'Failed to push due to a policy constraint on the branch'

Do you get more informative error messages when pushing manually from text terminal? — mbojko, Sep 16 '20 at 10:32
"The answer in this case is that the policy on the branch 'develop' does not allow direct pushes" OK, so you know the answer. Then what's the question? — matt, Sep 16 '20 at 13:39
Hey Matt, the question is where is the "output window for more detail"? — Sniipe, Sep 17 '20 at 11:29
I had this same isssue, nowhere in VS 2019 showed more info but in the end it was related to branch naming conventions on my repo. — Gavin Mannion, Dec 30 '20 at 10:52
This is a very niche case, but this error showed up for me during a Github API outage. — Mr.Technician, Aug 10 '21 at 16:55
I'm having the same issue. The output window - output from source control, has nothing useful at all. — Marz, May 16 '22 at 21:13

score 18 · Accepted Answer · answered Sep 16 '20 at 13:32

18

Have few reasons for this case:

Try pull, then push.
Check permission (you maybe haven't permission to push, after a change). You maybe push to just protected branch.

answered Sep 16 '20 at 13:32

Vy Do

46,709
59
215
313

I think I did push to a protected branch - my question is where do I find that? Perhaps VS2019 won't tell me this. – Sniipe Sep 17 '20 at 11:30
Ask your git repository's administrator. – Vy Do Sep 17 '20 at 11:33

score 10 · Answer 2 · answered Dec 15 '20 at 14:13

10

I was getting the same error and after trying lot of things, I found the solution.

Solution - Go to your GitHub account >> Profile >> Emails >> "Keep my email addresses private" - >> Uncheck this option.

Note : - This error may occur due to various reasons. This is the one of reason to fail the Push operation. To know the exact reason check your Output window in Visual Studio.

answered Dec 15 '20 at 14:13

Sudhir Yadav

124
1
9

Perfect! Worked for me also :) – Paul Williams Dec 29 '20 at 14:53
3

Would anyone no the answer for DevOps repos? – Doug Kimzey Apr 20 '21 at 15:40

score 8 · Answer 3 · answered Jan 07 '21 at 11:10

8

I had the same issue in VS2019.

I tried in CMD and got a better error message, which VS2019 did not provide

I had accidently commited a zip file in one commit, but removed it in the next commit.

So I had to reset both commits and remove the zip from the first commit. Then I could stage both commits and push them.

answered Jan 07 '21 at 11:10

Pavenhimself

527
1
5
18

1

This is the answer (or, at least a workaround) to the **actual** question: where are the "details" promised in the GUI error message? – Bob Sammers May 26 '21 at 11:51

score 4 · Answer 4 · answered Mar 01 '21 at 20:34

4

Had the same issue. Look at the Branch policies. Probably it needs approval or pull request.

answered Mar 01 '21 at 20:34

Rimmon Monson

51
2

yep that was causing my push to fail! – theITvideos Jan 06 '22 at 01:50
For me in Azure DevOps, "Automatically Include Reviewers" was turned on, so I could not directly push to the branch. I turned that off and it worked immediately! – AlbatrossCafe Jan 14 '22 at 05:07

score 4 · Answer 5 · answered Mar 10 '21 at 08:45

I had very same issue, different reason. I was pushing completely new branch from local, so I knew the branch policy could not be the culprit. But still it didn't allow me to push it, hence I needed some real error message. Trying to push from command line did the trick, unfortunately VS doesn't show these details.

You do not have permission to create ref 'refs/heads/XYZ...'. Please ensure the ref naming convention being used is allowed in this repository.

Indeed, I missed feature/ prefix enforced by latest repo policy change... So just another issue to check in case of issues.

Ash K · Answer 6 · 2022-12-22T16:13:59.453

For me, I was working off of my local feature branch that I cloned from master that looked like this: feature/MyBranchName

I was trying to push those changes to origin, but looks like a recent policy change prohibited pushing to feature branches which kept on throwing this error:

Error encountered while pushing to the remote repository: Failed to push to the remote repository. See the Output window for more details.

This command gave me the clue to the problem:

git push origin feature/MyBranchName (Remember to include the feature)

The message was this:

Total 0 (delta 0), reused 0 (delta 0)
To https://mycompanyname.visualstudio.com/DefaultCollection/TeamProjectName/_git/MyProjectName
 ! [remote rejected] feature/MyBranchName -> feature/MyBranchName (TF402455: Pushes to this branch are not permitted; you must use a pull request to update this branch.)
error: failed to push some refs to 'https://mycompanyname.visualstudio.com/DefaultCollection/TeamProjectName/_git/MyProjectName

My solution to this was to to merge changes from my local feature into local development branch, push the development changes to origin and using that development branch, make a PR to whichever branch I wanted to push these changes to.

score 2 · Answer 7 · answered Jun 21 '22 at 08:59

2

I had to set the value of "Bypass policies when pushing" to "Allow" for my user in ADO → Branch Security.

answered Jun 21 '22 at 08:59

MubarakZade

127
4
9

score 1 · Answer 8 · answered Jun 14 '21 at 10:30

1

Changing Git Options>Source Control>Git Repository Settings>Remotes Url to project URL worked for me.

answered Jun 14 '21 at 10:30

Aasish

377
5
18

score 1 · Answer 9 · answered Jul 12 '21 at 13:31

I had to set my git proxy, since I was behind a company firewall and using a proxy for http/https:

I opened a command prompt (and git was already installed on my Windows Server 2016 Dev box)
Typed in the following command after finding the server ip and port for my web proxy: git config --global http.proxy http://<ip address>:<port>
Typed in the following: git clone <clone address from Azure DevOps>
Worked like a charm!

P.S. I stole my answer from a similar Server Fault answer here: https://serverfault.com/questions/663504/can-browse-but-cant-ping

score 1 · Answer 10 · answered Jan 07 '22 at 11:42

1

If nothing shows up in the output, check 'show output from' set

answered Jan 07 '22 at 11:42

Andre

11
1

1

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jan 07 '22 at 15:38

score 1 · Answer 11 · answered Feb 09 '22 at 17:01

1

This happened to me & it wasn't creating a remote branch in my repo.

I was able to get around this in visual studio by going to Git->Manage Branches->highlight my branch & right click, "Unset upstream branch".

answered Feb 09 '22 at 17:01

James Burnett

151
1
5

score 1 · Answer 12 · answered Feb 16 '22 at 07:12

I was also facing the same problem. I tried to push from git bash. I got the below error message.

"(RefNames consisting of 40 hex characters are not allowed.)"

The character length of my feature branch name was greater than 40 characters. Because of this I was getting below error "Error encountered while pushing branch to the remote repository: Failed to push to the remote repository. See the Output window for more details."

I renamed my feature branch name to 40 characters and tried to push. It worked.

score 1 · Answer 13 · answered Jun 20 '22 at 10:15

1

in my problem , i have created branch then i deleted it from local but i didnot delete it from remote then i create another one with the same name then this problem appear .. so you can delete old branch from local and remote

answered Jun 20 '22 at 10:15

Mahmoud El Gaml

11
1

score 1 · Answer 14 · answered Jul 15 '22 at 00:38

1

Make sure that the branch being pushed has the exact name (case sensitive) as the origin branch you are pushing to.

answered Jul 15 '22 at 00:38

Terrible_ Theo

57
5

score 0 · Answer 15 · answered Aug 12 '22 at 03:31

0

There might be a policy defined on the target branch. for instant: main (TF402455: Pushes to this branch are not permitted; you must use a pull request to update this branch.)

answered Aug 12 '22 at 03:31

Masoud

260
2
9

score 0 · Answer 16 · answered Mar 03 '23 at 17:23

0

In my case there was a file (not included in the solution, but it was in the folder) that was bigger than 100 MB). Moved the file, retried with "Push" and it worked.

answered Mar 03 '23 at 17:23

Andrea Antonangeli

1,242
1
21
32

score 0 · Answer 17 · answered May 15 '23 at 16:11

For me the issue was a windows casing issue, the origin already had a folder structure, e.g. Feature/ I created a new branch under feature/ (lowercase) but Visual studio could only resolve it under the Upper case Feature/

Make sure your teams create branches with lower case format!

score 0 · Answer 18 · answered Jul 07 '23 at 15:13

0

I faced similar issue, actual issue was with the feature branch name, which was already used so I renamed and pushed, it worked.

answered Jul 07 '23 at 15:13

Santhosh UJ

28
1
9

Visual studio 2019 "Error encountered while pushing to the remote repository: Failed to push to the remote repository..."

18 Answers18