Make Http/Https switching in the UI more obvious #1020

Open
opened 2026-03-22 17:06:08 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @tenekev on GitHub (Feb 12, 2025).

I had the dumbest problem for 2 days. I'm a new user and still figuring things out.

I set up stacks, repos and syncs. I added the providers in the settings. And yet, somehow pushing always failed due to http being used instead of https.

First I went through the resources and realized that you need to clink on the Source git provider field to switch from http to https.
This is not at all obvious. and the change is literally a single letter.

Despite that, I was still having intermittent problems with authentication due to http. Until I went through the entire stack, for the 4th time and realized there is a protocol switch in the provider domain field. This little tiny obscure switch has haunted me for 2 days.

Please, make protocol switching a bit more obvious. I was looking for it and didn't find it. I know a frequent user won't mind but a novice finds it infuriating.

Image

Originally created by @tenekev on GitHub (Feb 12, 2025). I had the dumbest problem for 2 days. I'm a new user and still figuring things out. I set up stacks, repos and syncs. I added the providers in the settings. And yet, somehow pushing always failed due to http being used instead of https. First I went through the resources and realized that you need to clink on the Source git provider field to switch from http to https. This is not at all obvious. and the change is literally a single letter. Despite that, I was still having intermittent problems with authentication due to http. Until I went through the entire stack, for the 4th time and realized there is a protocol switch in the provider domain field. This little tiny obscure switch has haunted me for 2 days. Please, make protocol switching a bit more obvious. I was looking for it and didn't find it. I know a frequent user won't mind but a novice finds it infuriating. ![Image](https://github.com/user-attachments/assets/07c0630e-d9bd-4cc4-9281-7a22b200a05b)
GiteaMirror added the uienhancement labels 2026-03-22 17:06:08 -05:00
Author
Owner

@kapsh commented on GitHub (Mar 1, 2025):

Actual issue is at least three different layouts for setting up domains.

This one is used for git repositories on Repos and Stacks pages. Maybe most readable and obvious to use becase scheme is aligned in single line with domain and displays current value:

Image

These two are used on Settings/Providers page to create account

Image

and edit existing

Image

I believe your screenshot shows last one. Making all of them use first dialog would be a good start.

Though personally I'd prefer single URL field everywhere, as none of the git hostings or webgui I know has shortcut to copy repo path, usually there is button to copy full link (one can also copy from browser address bar or "git remote" output). Having three separate fields to enter this path is awkward, i.e. it's easy to get https://github.com/moghtech/komodo.git url while getting moghtech/komodo from it needs some pixel hunting.

@kapsh commented on GitHub (Mar 1, 2025): Actual issue is at least three different layouts for setting up domains. This one is used for git repositories on Repos and Stacks pages. Maybe most readable and obvious to use becase scheme is aligned in single line with domain and displays current value: ![Image](https://github.com/user-attachments/assets/a38b7cd9-5a50-41b2-a7f8-6944f7241b19) These two are used on Settings/Providers page to create account ![Image](https://github.com/user-attachments/assets/473495c7-a79b-4f1b-8896-d04993b3f4be) and edit existing ![Image](https://github.com/user-attachments/assets/c7acebeb-4550-41ad-98dc-16fdfaf76021) I believe your screenshot shows last one. Making all of them use first dialog would be a good start. Though personally I'd prefer single URL field everywhere, as none of the git hostings or webgui I know has shortcut to copy repo path, usually there is button to copy full link (one can also copy from browser address bar or "git remote" output). Having three separate fields to enter this path is awkward, i.e. it's easy to get https://github.com/moghtech/komodo.git url while getting moghtech/komodo from it needs some pixel hunting.
Author
Owner

@tenekev commented on GitHub (Mar 1, 2025):

Ideally, I'd like plain text fields that are parsed to extract the protocol. There is nothing more confusing than constructing the right URL from a mismatched UI of toggles, fields and hints. It looks good but it's less than functional. Many UIs fall victim of this practice.

@tenekev commented on GitHub (Mar 1, 2025): Ideally, I'd like plain text fields that are parsed to extract the protocol. There is nothing more confusing than constructing the right URL from a mismatched UI of toggles, fields and hints. It looks good but it's less than functional. Many UIs fall victim of this practice.
Author
Owner

@mbecker20 commented on GitHub (Aug 26, 2025):

Yes it was not the best choice, but it was a choice.

@mbecker20 commented on GitHub (Aug 26, 2025): Yes it was not the best choice, but it was a choice.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#1020