<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=23704) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=23704) </details> <!--IssueSummary end--> Now that my gitlab-ce!19911 is merged and we're running with SSH certificates I noticed that the clone protocol on project pages is always https. This is because of the change discussed in https://gitlab.com/gitlab-org/gitlab-ce/issues/3504#note_2872589 implemented in https://gitlab.com/gitlab-org/gitlab-ce/commit/88217029fc37e972fd84aec7eb9a77247a9532bf If I upload an SSH key it'll show "ssh" as the default. Similar to my gitlab-ce#49953 this is probably something that should get a global config setting, maybe we should just add one saying "ssh certificates are in use" to cover this, the issue in gitlab-ce#49953, and anything else that may come up.