Color gradient for files age

[slavaGanzin]

Description

Hi

I'm constantly looking for new GitHub projects and one thing that I care the most is maintenance activity (e.g. date of last commit).
So, I created a little extension, which runs only on GitHub pages. So fresh commits would become green and old — red.

Array.from(document.querySelectorAll('[datetime]')).map(x => 
  x.innerHTML = `<span style='filter: sepia(1) saturate(80) hue-rotate(${100 - 25 * (new Date() - new Date(x.getAttribute('datetime')))/(365 * 24 * 60 * 60 * 1000)}deg);'>${x.innerText}</span>`
) 

You can paste this in console on any repository page

Maybe it would be interesting for you to merge if I would create a PR?

Screenshot

Example URL

https://github.com/refined-github/refined-github

[yakov116]

Interesting idea. However a repo may have many files on the root that are never modified, giving a wrong impression.

I'm -0 on this.

[fregante]

The feature is reasonable and it would match the blame page. The only issue I see is ensuring the colors are accessible and native-looking. We can try using the colors from the blame page itself. Mockup welcome.

[slavaGanzin]

@fregante I was misguided by blame colors: red is a color of problem, while green is a color of change. It's natural: like fresh crops, and autumn leaves. Maybe, it would be better to make fresh changes green, and old - pale yellow/red? I think it's not a problem that .editorconfig is old, so it shouldn't be red.

[fregante]

Red and green are not good for this purpose. Try blame colors as suggested, with the same frequency (i.e. only color the new files, not all) https://github.com/refined-github/refined-github/blame/main/contributing.md

[slavaGanzin]

I dont think this way

[kidonng]

The feature is reasonable and it would match the blame page.

Thanks for the reminder, I remember there is something similar on GitHub already but cannot find it.

I was misguided by blame colors: red is a color of problem, while green is a color of change.

@slavaGanzin I'm also interested in this feature, however as opinionated as it is, we should try to blend in with GitHub's own style as much as possible. Especially given there's already this drama about issue color ("red or purple").

[kidonng]

Reopening since the feature request itself is valid. We can go through implementation details later in the PR, not to mention colors can be easily overridden with custom CSS.