10

Man fuuuuuuck, there's nothing more frustrating and scary than fucking up a local git repo. Because you know for a fact you won't be able to restore it

And I even had god damn backups of the .git folder. But reverting leaves me with more files than I started with fuuuck

Comments
  • 1
    Are you using a local git server or you just keep your repos without pushing anywhere?
    Try ro find a safe commit to checkout from.
  • 0
    @EddieBro Just a local repo. Thing is, I can't put it up somwhere because it's for work (confidentiality and stuff) and I don't yet have access to our internal git server
  • 1
    @12bitfloat that sounds like a "them" problem.
  • 0
    @sariel Not if I'm responsible for meeting deadlines lol
  • 0
  • 0
    just use any server, it's much better, even if it's local
  • 0
    use "git reflog" instead of "git log"
  • 3
    @12bitfloat sounds like they failed to give you the tools to succeed.

    If this is how they treat someone at the beginning of the employment relationship imagine how they'll treat you over the next year.

    I've hired many devs in my time. After HR is finished with them the first thing that happens is access to the source.

    Usually they make their first pull one or two weeks later.

    You're blaming yourself for something that's not even entirely your fault.

    Yes, you deleted progress. But you only lost that progress because your team lead is dragging their feet in delivering you access to the toolset.
  • 1
    You can do a "git clone" from the .git folder, e.g. "git clone '/path/to/.git' ".

    Pushes will be rejected though.
Add Comment