I use Azure Devops to host Git, and every day, when I do my first pull/fetch/push of the day, the Git Credentials manager pops up and asks me to Authenticate. After agreeing, it generates a new PAT on my account and uses that connection all day. The next morning it will ask for authentication again and it will generate a new PAT, even though the prior one isn't set to expire until 2025.
I have hundreds of PATs called "Git: https://<companyAddress> on <computerName>" with permissions on Code (Read & Write); Packaging (Read).
I've created my own PAT and went to the Tools > Options > Authentication and delete all references to DevOps and re-set it up with the PAT. I get the Authentication OK green checkmark. As soon as I go and do a fetch, I get the credential manager again asking for my windows auth. If I click cancel, it fails and tries again, showing the auth screen again. If I accept it generates a new PAT and works for the rest of the day. I fully expect tomorrow it will ask again to authenticate myself and make a new PAT for me.
I've tried uninstalling and deleting SourceTree and Altassian folders from AppData/Local and AppData/Roaming, and that didn't help either.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.