mutilate | Mutilate : high-performance memcached load generator | Performance Testing library

Is this a bug in dev.azure.com's way of doing GIT? Why have a "username" at all if it > > gets ignored anyway?

Nope, this is the expected action since you are using Git Credential Manager (GCM) to generate the password.

In fact, it is not an officially password. What it generated is a Personal access token after you click the button Generate Git Credentials, and its scope only to Repos(Read&Write).

At this time, go Security(https://dev.azure.com/{orgname}/_usersSettings/tokens) page, you will see there has one token be added which Token name is like git: https://dev.azure.com/{orgname} on {machine platform}.

For Personal access token, I'm sure you'd known that the PAT token are tied to a single user account when it generated. In another word, you doon't need input the username additionally while using PAT as authorize method. That's why the username get ignored anyway.

You can also check this doc to get How the Git Credential Managers works

Is this something I need to worry about?

Just treat it as password to keep secret will not cause too much issue.

Most of time, you don't need worry it. Because this token will expired very soon, will not longer than 1 day.

Also, as I mentioned above, the scope of this token are only to Repos with Read&Write permission. Even if someone accidentally gets this token, they can not make operation outside the Repos.