@0xabad1dea Put that as a feature request change for #forgejo. I like Forgejo, I run it on my own server -- but it is a fairly slavish copy of #GitHub, and there are some things, such as your suggestion, that could be done better.
### Needs and benefits Now that I did some user research in Forgejo, I can say with perceived high confidence that **users browsing code** and **users reading the README** and some stats are **disjoint subsets** π. This means it likely makes no sense to have one page that tries to cater for thei...
The problem i would have with that is that the file list generally shows not that many lines because the top level of most repos will have mostly just some subdirectories, while the Readme can get very long for some repos. That would mean a lot of scrolling to get to the file list in those repos.
Now if they made both the file list and the readme collapsible and maybe even start with the file list collapsed, then i think that would be a better solution.
@0xabad1dea I wrote this small Greasemonkey script to try it out, not sure it will always work:
π πππππ .ππππππ = (πππππ) => {
πππππ ππππππ = ππππππππ.ππππ΄ππππππππ±π’π²πππππ½πππ("πΎπππππππ πππππ΅ππππ-ππππππ__π±ππ‘_π·--π‘ππ0π")[0];
πππππ πππππ = ππππππ.πππππππ½πππ.ππππππ²ππππ;
ππππππ.πππππππ½πππ.πππππππ±πππππ(ππππππ, πππππ);
};
When the README is too long, it's a little bit of a hassle.