rrobin@lemmy.worldM to Community Code Reviews@lemmy.world · 1 year agoA trace of the Neovim providersplus-squareportal.mozz.usexternal-linkmessage-square0fedilinkarrow-up11
arrow-up11external-linkA trace of the Neovim providersplus-squareportal.mozz.usrrobin@lemmy.worldM to Community Code Reviews@lemmy.world · 1 year agomessage-square0fedilink
rrobin@lemmy.worldM to Community Code Reviews@lemmy.world · 1 year agoRequest a Reviewplus-squaremessage-squaremessage-square0fedilinkarrow-up11
arrow-up11message-squareRequest a Reviewplus-squarerrobin@lemmy.worldM to Community Code Reviews@lemmy.world · 1 year agomessage-square0fedilink
rrobin@lemmy.world to Privacy@lemmy.ml · 1 year agoGitlab now requires phone number/credit card verificationplus-squarelemmy.worldimagemessage-square0fedilinkarrow-up11
arrow-up11imageGitlab now requires phone number/credit card verificationplus-squarelemmy.worldrrobin@lemmy.world to Privacy@lemmy.ml · 1 year agomessage-square0fedilink
minus-squarerrobin@lemmy.worldtoLemmy.World Announcements@lemmy.world•[Update: Failed again] Update to 0.18.1-rc.1 tried and rolled backlinkfedilinkarrow-up35·2 years agoAs any engineer who does ops can tell you - you did the right thing - the solution is always to roll back, never force a roll forward, ever. We should totally do pre and post update parties though. Even if the update fails we can have an excuse for drinks and a fun thread. linkfedilink
As any engineer who does ops can tell you - you did the right thing - the solution is always to roll back, never force a roll forward, ever.
We should totally do pre and post update parties though. Even if the update fails we can have an excuse for drinks and a fun thread.