Yes, you are generally right, as far as we are concerned only the personal keys. What I had in mind was more of a case where you have, e.g., "deploy keys" like for different CI/CD pipelines, using GitLab, Jenkins, GitHub, etc. -- then in some sense you can be forced to use (and manage) different keys.
If I get you comment right, of course. Anyways, it all depends on particular use-case, I guess.
Thanks for the comment! :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't know if identity by destination host is a good reason for multiple keys.
Those seem more reasonable. But still not sure.
Yes, you are generally right, as far as we are concerned only the personal keys. What I had in mind was more of a case where you have, e.g., "deploy keys" like for different CI/CD pipelines, using GitLab, Jenkins, GitHub, etc. -- then in some sense you can be forced to use (and manage) different keys.
If I get you comment right, of course. Anyways, it all depends on particular use-case, I guess.
Thanks for the comment! :)