GitLab

@AaronViviano We have some steps in https://docs.google.com/document/d/1GCK53YDcBWQveod9kfzW-VCxIABGiryG7_z_6jHdVik/pub … We're going to make sure our backup system is completely functional after this

@jimgree67936534 Thank you Jim. Glad you appreciate it! :)

@castaway01 Not yet. We're still on the restore phase. We will keep you posted!

@piamancini @sytses Thank you!

@netmanchris Thanks for the support. We're working on getting it fixed ASAP

@net_snow Did just that. We're currently on top of things, but if things get out of hand, we'll have you in mind

@Negan1911 Thanks Nahuel! We will keep posting updates :)

@Jalai_Amitahl Absolutely! He is awesome :D

@WhySoAaron Thank you for your support. Appreciate it. Working on getting this fixed. Sorry for the trouble this has caused.

@Rtzq0 Thanks Jason! We're glad for all the positivity about this!

@net_snow Thank you for your support. Appreciate it. We're deeply sorry for the trouble this has caused.

@RodrigoAvila I'm not sure what do you mean exactly by this? Could you explain a bit? You can redirect with JS

@mootpointer We'll definitely rectify this, so there isn't a next time.

@gonedark Tres commas is killing us all

@carty64 Thanks Jeff! We will keep posting updates. Feel free to check the document.

@ReadyJared Thank you for the positive thoughts. We're working on getting it fixed ASAP

@reidbrokeit Definitely. We're making a list of things to go over after this is dealt with.

@sharma_nishant2 We're not sure. We're still working on the recovery procedure.

@jasonrm Thank you! And absolutely... We hope this helps everyone to avoid similar situations!