Github never deletes commits so we just need to find the hash for the latest one before the force push. In the forks you can find ones from before, but they're not up to date. Example: b5c8280d87c501d9ca7f63a6f252ca60ca820a4a for a copy 3 months old
Link: https://github.com/Azure-Samples/azure-sql-db-vector-search/...
blibble|11 days ago
the merge commits in those repositories are all digitally signed by GitHub public key, so the previous history is fully authenticated and non-repudiable
so any copies now can be trivially proven to be genuine output by Microslop
hoisted by your own petard
signed merge commit is: 987eee6af61788647ae0cab82ae8a5d9402a5bd0
PGP signature (using GitHub's key: B5690EEEBB952194) is:
for posterity:
basch|11 days ago
cookiengineer|11 days ago
The biggest irony would be if the page itself was generated by an LLM.