Github Token Scanning is no longer retroactive

[onerandomusername]

Description

Github Token scanning does not work on gists at all anymore

Steps to Reproduce

upload a valid token to a github gist.

Expected Behavior

the token is invalidated by discord.

Current Behavior

the token is left active and nothing occurs

Screenshots/Videos

No response

Client and System Information

any

[night]

Do you have an example token we can take a peek at?

[onerandomusername]

Yes, I can send you a valid one via Discord, as I am not able to send one here due to not having a bot with an older token that I can access.

If you need a now-invalidated token, here is one: ODA2MTcyMzE3MzY1NDM2NDI3.YBlkeg.z4lJ4NCAkKa6cnDygeuiqFPUxdE

[appellation]

This issue no longer occurs.

[onerandomusername]

This issue no longer occurs.

@appellation You're right: It doesn't matter if its an old or new token, when uploaded to GitHub Gists they are not invalidated.

[appellation]

I'm unable to repro this issue. I uploaded a valid token to a public Gist and it was invalidated as expected.