GitLab.com is currently offline due to issues with our production database.
We accidentally deleted production data and might have to restore from backup. Google Doc with live notes https://docs.google.com/document/u/1/d/1GCK53YDcBWQveod9kfzW-VCxIABGiryG7_z_6jHdVik/pub.
We’re working hard to resolve the problem quickly. Follow GitLabStatus for the latest updates.
This topic is now a banner. It will appear at the top of every page until it is dismissed by the user.
Now that GitLab.com is back online, will official guidance from GitLab be forthcoming with actions users should take to verify the integrity of their repos and merge requests? I’ve seen a tweet that suggests one action users should take related to mr, but this seems a haphazard way to communicate.
This topic is no longer a banner. It will no longer appear at the top of every page.
Yep, a detailed postmortem blog post is in the works. For the time being you can check the draft in https://docs.google.com/document/u/1/d/1hOzpk3dOhzrlvZH-TrjCGZHC2p_a5Rb6C8mFDcZU0W8/pub (that was linked in the mortem doc), and also follow or leave your comments in the issue https://gitlab.com/gitlab-com/www-gitlab-com/issues/1108.