all 16 comments

sorted by: hot top controversial new old
[–] 23 points 1 year ago (3 children)
  • [–] 7 points 1 year ago (5 children)
  • [–] 8 points 1 year ago (4 children)

    Rebase still means you have to resolve conflicts, but it can be worse because you may have to resolve conflicts across multiple commits that you're rebasing on top of a conflict.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 1 year ago* (1 child)

    In my experience this can be beneficial when committing and rebasing small and distinct changes.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    Agreed. If your commits are reasonably structured, rebasing is far more helpful.

    Although these days I usually opt for one ball-of-mud commit while developing the code, which is always fairly trivial to rebase - only one commit, can't have follow-up issues - and then I redo the commit structure from scratch as a part of preparing the code for the benefit of the reviewer.

  • source
  • parent
  • [–] 6 points 1 year ago
    [–] 2 points 1 year ago

    I thought it was just me who has a hard time with git. I feel better now.

  • source
  • [–] 1 point 1 year ago

    I like that the suicide prevention number is wrong. It should still dial, but funny.

  • source
  • [–] 1 point 1 year ago (1 child)
  • [–] -1 points 1 year ago

    AI tools are actually really helpful with this kind of stuff. Not with actually resolving the conflict, but with setting things up so that you can see and reason about it.

  • source
  • 57 comments in c/programmer_humor@programming.dev view that post
    [+] 101 points 1 year ago (14 children)
  • [–] 70 points 1 year ago (10 children)

    It is a duplicated repeating error because this clownshow of a website is managed by squirrels and ducks. 1-800-273-8255 would be a valid US number. Doubling 273-8255 is not, but probably vibe coded under management that should be purged by these results.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 6 points 1 year ago (7 children)
  • [–] 6 points 1 year ago (3 children)
  • [–] 7 points 1 year ago (2 children)

    Lmao not willing to do the phone math rn, does that actually fit the numbers?

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (-1 replies)
    [–] 28 points 1 year ago

    “Proper way to commit after merge conflict” sounds like a robot trying to save a relationship after a bad sex experience

  • source
  • [–] 24 points 1 year ago (9 children)
    git reset --hard <commit-hash>  
    git push -f origin main  
    

    i didn't see anything, officer

  • source
  • hideshow 9 child comments
  • [–] 18 points 1 year ago (8 children)

    You should be forcibly kept away from production systems...

  • source
  • parent
  • hideshow 8 child comments
  • [–] 12 points 1 year ago (2 children)

    We had an intern do this once. We changed our server config to make sure it wouldn’t accept such operations.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 year ago (4 children)

    Never use --force. Always use --force-with-lease.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 1 year ago (3 children)

    I've mistyped that a couple of times to be --force-with-leash

  • source
  • parent
  • hideshow 3 child comments
  • [–] 16 points 1 year ago (2 children)
  • [–] 32 points 1 year ago

    It's never too late to git merge --abort!

  • source
  • [–] 12 points 1 year ago (1 child)

    calls suicide hotline to ask for tech support

  • source
  • hideshow 1 child comment
  • [–] 10 points 1 year ago (1 child)

    Keep your commits small. Merge often. That will reduce the likelihood of terrible merge conflicts.

    If you’re not sharing your work with your team mates for a long time, then you’re setting yourself up for trouble.

  • source
  • hideshow 1 child comment
  • [–] 9 points 1 year ago

    Jujutsu (which is compatible with git) has a nice conflict resolution flow that doesn't break you workflow.

    Conflicts are encoded into the commits, so that there is never a weird in between state that you have to deal with immediately before being able to do anything else.
    Then you can use Jujutsu's easier history manipulation to resolve the conflict in the conflicted commits.

    https://steveklabnik.github.io/jujutsu-tutorial/branching-merging-and-conflicts/conflicts.html

    And you could always jj undo if you did something you didn't want to.

  • source
  • [–] 8 points 1 year ago (1 child)

    Been there too OP. Not a good place.

    It's usually easier to find another job, it will reset your mind, and fear won't be driving you.

    Or you could just commit what you have, comment "YOLO" and auto resolve conflicts and push.

  • source
  • hideshow 1 child comment
  • [–] 7 points 1 year ago

    I remember when similar screenshots circulated for how to tell if i am running jdk or jre, which is even more surprising.

  • source
  • [–] 5 points 1 year ago*

    See I wasn't really going to kill myself today, but the thought of dialing that long ass number is just to much.

  • source
  • [–] 4 points 1 year ago (1 child)

    in life you commit to many things. you commit to yourself, to your partner, to happiness, to legacy.

    when we die, is that like a push to origin?

    when we die, do our commits all go to the big repo in the sky?

    is god the maintainer? when you pray is that like a bug report?

    so many questions...

  • source
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    Little branch, as our master says: We all have our feature to accomplish. Once our feature is complete, our faith will be up to the maintainer. If you were a well behaved branch, you will be allowed to merge with the master. If you weren't so, you'll be deleted and burn In the flames of reflog.

  • source
  • parent
  • [–] 3 points 1 year ago*

    If you git help, you could hash things out, rebase your commitments, and push forward to a better life. Then again I could just be cherry picking things.

  • source
  • [–] 3 points 1 year ago*

    My best friend when I fuck a commit up: https://ohshitgit.com/

  • source
  • [–] 3 points 1 year ago*

    Google gives you results based on your prior search history.

  • source
  • [–] 3 points 1 year ago (1 child)

    git is like a minefield. stray away even a little bit from standard path and you are done for. I had git multiple times throw some obscure errors at me when trying some commands and then trying to undo/recover. how's "undo" is not a git command I don't understand.

  • source
  • hideshow 1 child comment
  • [–] 6 points 1 year ago (1 child)

    No merges allowed. Rebase only.

  • source
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    Commit branch...I see your thinking of hanging yourself, here is a link to tying a noose

  • source
  • [–] 2 points 1 year ago* (5 children)

    I don't get why people have such problems with this they even make memes about it.

    Have you people never merged anything by hand or what? It's really not hard.

  • source
  • hideshow 5 child comments
  • [–] 4 points 1 year ago (2 children)

    it's fine for simple merge conflicts but it quickly gets messy when the two branches are trying to do opposite things to the same code

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago
    [–] -3 points 1 year ago*

    So cool, I havent seen an ad like this in at least a decade. I use something called an ad blocker and also I switched to Kagi, so.... :)

  • source