克隆菜单的长度 ( Clone menu length )

[lutinglt]

The advantage of Github's length is that most cloned addresses can be viewed in full
The length of Gitea is less white space for buttons

Gitea:

Github:

Which style do you think is better for the length of the clone menu?

@Felitendo
@georglauterbach

[Felitendo]

I prefer Gitea’s implementation if I'm being honest. It feels much cleaner than GitHub’s. In my opinion, seeing the full address bar for the clone URL isn’t particularly important, especially since GitHub’s version will run into the same limitation anyway.

[lutinglt]

I feel the same way too

[lutinglt]

If I shrink it smaller, will it feel better?

smaller1:

smaller2:

smaller3:

gitea:

[georglauterbach]

From a UI perspective, the smaller menu is neater. From a security perspective, not seeing the full URI is a no-go.

IMHO, making it too small is not a good idea, but keeping it a bit smaller than the one on GitHub is probably fine. I, personally, prefer GitHub's look, but I can live with Gitea's too.

[Felitendo]

From a security perspective, not seeing the full URI is a no-go.

Sorry but I have to disagree with you. I don't think anyone is looking at the URL that is on the "clone box". Most people just look at the URL in their browser. Also the chance that a user clones a url from a Gitea Repository that you host yourself is very low

[lutinglt]

In fact, if the length of Github's repository name is slightly longer, it cannot be seen as complete. From a security perspective, is it only necessary to ensure that the domain name can be seen?

I carefully examined the cloning menu of Github again, and the most harmonious aspect of Github's length is that it has longer description content filled in this section, and there are only two buttons in the menu with relatively long content.

I have an idea, I want to make it a custom option, just add this CSS variable in the theme to control the length

:root {--custom-clone-menu-width: 200px}

Of course, it will have a default value, as well as a maximum and minimum value, and then explain it in the documentation. My previous idea was to DIY themes through source code, perhaps I could define some custom CSS variables to meet some lightweight DIY needs, and heavyweight ones through source code

@georglauterbach
@Felitendo

[Felitendo]

Sounds good and even though I don't agree with GitHub's Design choices, this is still a Gitea Theme that aims to mimic GitHub's Design as close as possible. I think the reason that GitHub's Clone Box is so long is because it has "Codespaces" as a second tab on the top. You can't implement this in Gitea through a Theme though and for that reason, i think it's best to stick to the "Gitea smaller1" version by default

[lutinglt]

I initiated a vote #6
@Felitendo @georglauterbach

[georglauterbach]

I like approach of having a variable for this. With this approach, I can live with any default length.