Renaming a Repository in Azure Repos | Azure DevOps
Azure DevOps gives you a lot of flexibility as far as repos are concerned. It gives you the ability to rename the repo in easy steps as shown below.Also renaming a repo won’t affect...
Category: Azure Repos
Import Github Repository into Azure Repos with history | Azure DevOps
There are many ways in which can add code & files into a repository that has been created. Azure DevOps also provides different ways to add code/files and one of them is import the...
Import Azure DevOps Repository from another Azure DevOps Project
In this article, let us see how to import an Azure DevOps GIT Repo from a project into another project in the same Azure DevOps organization. All the GIT history from the source repo...
Create a new repository in Azure Repos | Azure DevOps
To create a new repository in Azure Repos, you should be either an Project Administrator or a member in the Contributor group with basic license access in Azure DevOps. An Azure Devops Repository can...
How to delete a branch in Azure DevOps Repository?
We have seen about how to delete a repository in Azure DevOps. When there are too many branches., it becomes necessary to delete branches & keep it to a certain number so that team...
Restoring a Deleted repository in Azure DevOps
Though there are no direct ways to restore a deleted repository in Azure DevOps, By using Azure DevOps REST API it is possible to restore a deleted repository as the deleted repositories go into...
Delete Repository permission for a specific Repo in Azure DevOps
Giving delete permissions to all the users for a repository might be unnecessary as there is a chance of repository getting deleted mistakenly by someone from the team. To prevent this it’s neccessary to...
Setting Delete Repository Permissions for an Project in Azure DevOps
In Azure DevOps, when a project is created all the users belonging to Contributor group will have delete repository permission by default. It becomes necessary to assign delete repository permissions only to a certain...
error: cannot lock ref ‘refs/remotes/origin/xxx’: there is a non-empty directory ‘.git/refs/remotes/origin/xxx’ blocking reference ‘refs/remotes/origin/xxx
This issue usually occurs when there are 2 branches with conflicting names. Suppose let us say you have a branch “QA” and when you have another branch with a name something like “qa/feature/test”, then...
cannot lock refs/remotes/origin/xxx/xxxx : ‘refs/remotes/origin/xxx’ exists
This issue usually occurs when there are 2 branches with conflicting names. Suppose let us say you have a branch “Dev” and when you have another branch with a name something like “dev/hotfix”, then...
