Because the `microsoft` group account is the owner of the repo. With group accounts, you can designate many individuals to have admin access to the repo, but the actions taken by those admins will be attributed to the group account that owns the repo. (Because presumably the rest of the admins agree with the action taken, otherwise they would undo it).
Because the `microsoft` group account is the owner of the repo. With group accounts, you can designate many individuals to have admin access to the repo, but the actions taken by those admins will be attributed to the group account that owns the repo. (Because presumably the rest of the admins agree with the action taken, otherwise they would undo it).