Conversation

Notices

1. lain (lain@lain.com)'s status on Saturday, 25-Jul-2020 08:50:38 JST lain

   in reply to

   • kaikatsu
   • winter
   @kaikatsu @velartrill what the heck are you even doing stop sharing 3gb of make up tips on discord git
   • バツ子（痛いの痛いの飛んでけ;; likes this.
   • kaikatsu (kaikatsu@blob.cat)'s status on Saturday, 25-Jul-2020 08:50:40 JST kaikatsu

     in reply to

     • winter
     @velartrill @lain I use git because it's much better than "oh I made a fucky wucky I gotta go find an old download of my release now"I also use it for like 3GB releases too so it gets messy.
   • winter (velartrill@pleroma.site)'s status on Saturday, 25-Jul-2020 08:50:41 JST winter

     in reply to

     • kaikatsu
     @kaikatsu @lain this is how i use it too, when i absolutely have to use git
   • kaikatsu (kaikatsu@blob.cat)'s status on Saturday, 25-Jul-2020 08:50:42 JST kaikatsu

     in reply to
     @lain Lain, in the words of Alex Jones - I'm kind of retarded. I just go git add . and git commit -m and frantically google how to reverse bad commits. I need the real spoonfeed.
   • lain (lain@lain.com)'s status on Saturday, 25-Jul-2020 08:50:43 JST lain

     in reply to

     • kaikatsu
     @kaikatsu maybe check out 'git flow' for inspiration
   • kaikatsu (kaikatsu@blob.cat)'s status on Saturday, 25-Jul-2020 08:50:44 JST kaikatsu
     Can anybody who understands git (if that exists) help me out here?I pushed a version for release. Then I started committing features for the next unreleased version. But someone reported a bug with the version I pushed before. What do I do from here? Do I stash my new changes somehow? Do I stash and then branch the new changes, and maintain beta and stable branches instead?