[peterth3]

Thats a lot of work for GitHub: 1) Find a backup from before this change was made. 2) Restore backup on new db instance separate from prod. 3) Export star gazers list for this one repo to CSV or something. 4) Destroy instance restored from backup. 5) Execute admin script with CSV against production database to insert lost stargazers.

This gets even more complicated if GitHub has more than one central database, which I’d assume they have something like sharded mysql.

Considering that they made the change acknowledging that it would destroy their stargazer list in the confirmation dialog, it’s unfair for them to expect any help from Github’s support recovering that list.

[saleemkce]

Hmm. that's aweful list of things to revert back. Sure it seems difficult to revert back in production systems.