Skip to main content

Azure DevOps Server- Update Git credentials

Oh no, after writing a lot of posts about what I thought would be an easy operation, I'm back again with a last follow up post on moving an Azure DevOps Server instance from HTTP to HTTPS.

If you missed the previous posts:

In this last post(I really promise) I want to talk about Git Credential Manager.

Git Credential Manager simplifies authentication with your Azure Repos Git repositories. Credential managers let you use the same credentials that you use for the Azure DevOps Services web portal.

It can be installed as part of Git for Windows and thanks to it you don’t need use SSH keys or Personal Access Tokens to connect to your Azure DevOps Git repositories.

The problem was that after switching to HTTPS my Git credentials no longer seemed to work. Instead when I tried to do a git operation, it failed with the following error message:

$ git pull
fatal: Authentication failed for `repo url/`

To fix it I had to remove the existing credentials. Therefore I went  to Control Panel -> Credential Manager.

In the list of Generic Credentials I searched for the git repo credentials and clicked on Remove:

After that the authentication pop up reappeared and I could reenter my credentials.

    Labels:

    Popular posts from this blog

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
    Read more

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
    Read more

    VS Code Planning mode

    After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
    Read more