> Struggling with permission issues when accidentally pushing from a wrong identity file
This is basically only a problem with Azure DevOps, which has a completely broken SSH implementation. It accepts any key, and only later checks permissions. Other source forges do not have this issue, as they only accept keys that have access.
So basically, this might be convenient if you use Azure DevOps, but otherwise there should be no need whatsoever.
This is basically only a problem with Azure DevOps, which has a completely broken SSH implementation. It accepts any key, and only later checks permissions. Other source forges do not have this issue, as they only accept keys that have access.
So basically, this might be convenient if you use Azure DevOps, but otherwise there should be no need whatsoever.