-
Notifications
You must be signed in to change notification settings - Fork 123
Refs already exist #567
Comments
The workaround is usually to find the existing branch with that name in git, and merge or delete it. |
That's what I thought initially, only the branch is non existing. Maybe because of multiple project with the same package upgrade? So it creates the same branch x times? The naming is not unique, maybe we should change it to |
That's odd. I'm not a git expert, I don't know how a |
It works at: https://github.com/MarcBruins/nukeeperrefissue and at my private ado account. Not sure what is going on now. I'm certain the branch is deleted. If i don't delete the branch i get the following error: which makes sense and is different from the error above. The difference is that our project is way more complicated. The Asp.Net.Core dependency is used in 10 projects instead of 2. Will investigate some more(next step is to run the local repo command on a specific project) |
Issue is solved magically? Maybe ADO still had some reference to the branch somewhere after all. Closing it for now |
I'm getting similar error when using NuKeeper extension for Azure Devops. Here's a bit censored tail of detailed logs:
I'm sure that branch doesn't currently exist on remote.
where 2 things seems incorrect. First is running checkout in .git\ subdirectory and the second one is doubled origin in that checkout command. In both situations I've run extension task with Also I saw that in both situations logs are starting with:
so it's not using both I can provide more info if needed. |
Is there a branch in the branching tab on azure devops? |
There's a |
Should I create separate issue or maybe that one could be reopened? |
I'm running into the same issue on Azure DevOps:
There exists no such branch. |
I'm running into the same issue on Azure DevOps. Did this get solved? |
@AnthonySteele I'm running into the same issue too. Azure have no such branch, but issue still appear.
|
On the project i'm working on i get the following exception:
2018-11-27T14:53:25.4275277Z Updating'Microsoft.AspNetCore' from 2.1.0, 2.0.3, 2.1.2, 2.1.4 to 2.1.6 in 10 projects 2018-11-27T14:53:25.4300247Z Updates failed NameConflictException : failed to write reference 'refs/heads/nukeeper-update-Microsoft.AspNetCore-to-2.1.6': a reference with that name already exists.
Might be related to: GitTools/GitVersion#864 but i'm not sure yet.
The text was updated successfully, but these errors were encountered: