Example page: https://codeberg.org/GramEditor/gram/releases

Just like on Refined Github, we should show a heatmap for download counts.

Got it, thanks! ❤️ Merged in 47d010b4500f953f178ace3e435c7745daf109ac and reformatted a bit in 32cb8b9a56550c45541942de779a6a2553b4ee7e.

Thanks for the PR! This change makes sense to me. Can you explain what you mean with the missing }?

When a file list takes a while to load, relative time heatmaps may not immediately work. This is because we only look at timestamps at the start of page load rather than using MutationObserver to find newly created <relative-time> elements.

Oh, I misunderstood. Indeed, I removed it from view_file.tmp already. I thought your 2 comments were separate 😅

Arguably, sorting by file date doesn't solve the problem of seeing the difference between "3 months ago" and "3 minutes ago". Furthermore I personally have never looked at Github or Forgejo file listings as a traditional file explorer, so I don't really agree with that comparison or requirement of relevancy.

It sounds like we have a fundamental disagreement, so I'll leave it at this. Maybe I'll have to make a "Forgejo Refined" extension after all 😛

I agree that "wanting to verify if my file was uploaded" and "check if any file is changed at all" is a poor reason for this change, and is perhaps poorly worded in the original post. However, those are not the only things mentioned in this thread.

Click "Expand to see screenshot" in the original post or the attached screenshot that I happened to run into the other day (on Github, on a machine that did not have Github Refined). Seeing the difference between "3 months ago" and "3 minutes ago" is very tough, but if they are color coded it's immediately clear that there was activity there.

Additionally, this ties into the following reason I gave above:

Colorful highlighting makes it immediately very obvious, and makes it very clear which files in the project are commonly changed. If you're exploring a project's code, you may want to start by looking at those files.

For what it's worth, I think both the repository page redesign and this feature can co-exist and don't have to be mutually exclusive.

Judging project activity by making a noisy colourful code history view is a terrible workaround IMHO.

Should I also add a test for the frontend side of things?

Amazing, thank you!

I am maintaining a Go package called "fire", currently at gofire/fire. It looks like /fire is currently returning a 404 so I am unsure what its status is, but it would be really nice to be able to drop the "go" early on.

Not sure about sorting, because it requires an extra click, and folders are also a part of this which usually only appear at the top. Being able to see it at a glance with a color is a lot easier.