This, in and of itself, is a major flaw in their documentation. It's like PHP's mysql functions not mentioning escaping strings on their manual pages, but instead burying it all entirely elsewhere, where you'd never think of looking.
"You should have read every single page of the documentation, then you'd know we briefly mentioned mysql_real_escape_string() and prepared statements that prevents this issue."
I mean, the least you can do if you won't provide a fix, or sensible defaults, is to make it abundantly clear you have to correct it yourself. (Bit of a broken record with this schtick, sorry!)
On the other hand, he did it in a largely non-malicious way and even managed to expose those Rails knuckleheads for the greater good.
Github should find a way to let him back in, intentionally. Perhaps they could offer him to create a new user and they could give him some of his repositories back (if any were important).
Edit: It appears Github has in fact reinstated him.
My prediction: Egor gets a job offer from GH within 2 months.
This 18 year old kid's actions made an enormous difference for good in the security of _every single user of GitHub_.
And for that, he gets banned. WTF.
GitHub needs to man up, say thank you, publicly apologize for banning the kid, and politely ask people in the future to send Rails exploits on GitHub to some.email@account they've set up to ensure they're dealt with promptly.
Claiming the "letter of the law" here is making GitHub look seriously petty and lame.