GitHub ninja tip: When you hit the end of the Blame or History page on vanilla/vanilla

Vanilla Forums
Vanilla Forums
in Dev & Ops

If you ever need to dig into the depths of Vanilla past the history-wiping commit snafu of Feb 12, 2012, this is the last commit before it: https://github.com/vanilla/vanilla/commit/688e3f751051907f26a848a07b4f6dc5fc7f10d3

From there you should be able to use that blob state to find any additional blames or history you seek.

You also CAN jump into commit history to arbitrary points in time using page numbers, despite GitHub now obfuscating that with its ?after=(hash) "more"-based pagination it uses now. This is the page the history-wipe commit is on today (this will change over time, of course): https://github.com/vanilla/vanilla/commits/master?page=426

The history wipe only applies to blame / history on the file level. The full commit logs are still there.

Comments

  • Vanilla Forums
    Vanilla Forums

    For the record, we did notice that history-wipe issue back in 2012. We still have no idea what caused it, and it was deemed too risky to try to rebase to fix it. We opened a GitHub support ticket and they were unable to help us, either. Just something we've learned to live with, and it led me to discover the details above long ago.

Categories