4 ms·
I don't think you can really trust commit history to deduce this: - the history can be rewritten, with push --force. The author might have iterated by force pu
by jraph 2y ago
I don't think you can really trust commit history to deduce this:
- the history can be rewritten, with push --force. The author might have iterated by force pushing one commit
- The author could have discovered it by change in a private repository, or another repository that they deleted
- wokwokwok 2y agoHonestly, I doubt the author is playing the “deep game” of looking like they’re just messing around while secretly being a secret agent and (for some fathomless reason) making it look like it with an artificial git history. So in general, yes, but in this case, I doubt it. I’m pretty sure this git history is a real and true log of them dicking about trying to get the exploit they saw on twitter working. …but, I guess, you could be right. /shrug
- jraph 2y agoI do occasionally force push myself, mostly for making my history look clean, not really secretly hiding stuff. And if I had to tweak / study a GitHub exploit, I would definitely force push to try stuff without leaving a trail for meaningless commits. It actually didn't occur to me that the author would do this for messing around, but it could be indeed. :-)