silverwind
silverwind
Yes, area is a bit smaller then on README for example, but there's no hard requirement on how wide a markdown rendering area has to be, so we should strive...
> Fair enough. I was slightly surprised that the README and Wiki don't use a shared markdown component. That would actually be a very good refactor for later.
Need to switch that to two-row layout on small screens like it's already done for PR review toolbar, e.g. https://try.gitea.io/silverwind/symlink-test/pulls/8/files.
Yes, agree there is too many buttons already. https://github.com/go-gitea/gitea/pull/20375 will remove one of them.
https://github.com/go-gitea/gitea/pull/20602 will consolidate a few more.
More conflicts appear. Will take a look at UI later. One question: What if the remote only supports RSA key or maybe it's HTTPS only? Is it something that can...
Generally I'd say `.git` folder should be included as that size matters for the server and client when they do a (full) checkout. Still, I'd be interested in what optimization...
So GitHub API must then give the size of the checkout, but I think it's the less interesting metric of the two.
I think we should probably get rid of the background altogether and just color the icon only in `--color-gold`, which works on both themes, e.g. add `text gold` classes to...
Thought, if we color these icons in that list we should color all other repo icons throughout the UI as well which is probably a lot of work. Let me...