Override not working

[Nixinova]

My repo's languages shows a .ts file as JS even though I have explicitly used an override because of #5251.

*.ts linguist-language=TypeScript

Caching wouldn't be an issue because this repo only has one single commit.

What would the issue here be?

[Alhadis]

What would the issue here be?

Pushing a change to .gitattributes will only impact classification once another change gets pushed, which forces GitHub to refresh its now-stale cache. When I forked your repository and pushed a minor change, I saw that cli.ts was being identified as TypeScript:

Though I'm not sure what's going on with the sidebar…

[Nixinova]

once another change gets pushed

Ah, alright.

now-stale cache

It was never cached in the first place, though.

[Alhadis]

It was never cached in the first place, though.

Since it's a background job queued in an already resource-intensive pipeline, I'd say it's deliberate—it's more efficient to pick .gitattributes rules up whilst you're scanning the repository the first time, rather than scanning every directory once for new overrides, then scanning them all again to compute language-stats.

That's just a blind guess though, as I've no knowledge of GitHub's actual internals.

[Nixinova]

Hm, Ive pushed two commits and the file has been reindexed but its still showing up as JS.

[Alhadis]

If you pop open the devtools, you'll see the same classes as those in my earlier screenshot. IIRC, there's some dissonance going on at the moment between Linguist and GitHub's indexing engine. I can never seem to remember which parts Linguist is responsible for, and which to blame on somebody else. 😂

[lildude]

Hm, Ive pushed two commits and the file has been reindexed but its still showing up as JS.

You've encountered this before 😉 This is the problem I described right at the beginning of my response at #5249 (comment)