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/...

it's even better than that

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:

    -----BEGIN PGP SIGNATURE-----
    wsFcBAABCAAQBQJnPIphCRC1aQ7uu5UhlAAAUgMQACyp7apkh0e413K7ipGd7Z+K
    JCMq93GoJm4OSgzzZzCp1DbeEq2u1mX1ZAXLq5XKqM0cL6cTg13IF4oumq8QmTzQ
    bFykqKfrkCDSTIa2v5CucJedmIoJl976jX96bnV8YXgoKx8/43044galo23bjoJ8
    9tUcVnC10FYj7NTI9/uCN9C3f2Up3t9xUaJzJv3OdgjJ9B3cNwYBfF6sDCj3QnUu
    AWRNdGIyqyO1WKnj2XL2Qo9jMWNX3uHSBYYGqIvZqu2bjpYS89Dt3X086JlLdQG9
    Pef2PHX6VeZ6j8J4NPqi28mB2n9Dn7V6q0SQIF1z4hsa9fLC0kljyrrO3T/RT6Ut
    D8r3Y7vjGUHPNkVXSo1oNCiNMV9LjDQwiJc/AuF6smupxivIFCKe8nDPBlCvi6gr
    uPz5KK5MfpmG5rO2+NA0LcrUPAk6F3nxDI46+Lsu2nCvO+pOauQQ+oUvxJNCnI3Y
    5PAReulGOZHXbiCj/9j6+H7rUBCGk2phVtXOsXxitCorigNXAeAJ8hP2cgjXZH25
    NGGtjyp75VVBydzSCz9yY+VypITovsDmEC1CxfbJRS7SaTdU7bGCLN08JcmfOzNb
    u/3iPkKMXXWMNYO6J1bUeAqVpueGkqsAqnhY32NylIni07Oz/he8nEsQCXC+4ueG
    uYgSpEu8IaERBIQLVntK
    =yDvq
    -----END PGP SIGNATURE-----

https://github.com/Azure-Samples/azure-sql-db-vector-search/...

Pretty interesting seeing the escalation process at Microsoft at work, and the censorship (well, damage control) attempts.

The biggest irony would be if the page itself was generated by an LLM.