5

GRAARGHHHHHHHHHHHHH POOHHHHHHHHHHHHH!!!

That's just my frustration with SourceTree.

This is a story all about how my SourceTree got twisted upside down, and I'd like to take a minute to just sit right there and tell you how I pushed my code to my repository on GitHub:

Iiiiiin my SourceTree, born and raised, I checked out my branch, tried to push but SourceTree said: "See ya later!" (denied/authentication failed). Sssoooo I told myself I was not going to use ChatGPT to solve this problem. I was going to use my Medior skillzzzz1!1!1!Oen and so I did solve it, but what a fucking hassle!

First I tried to remove all credentials from SourceTree and from my system, then I tried to add a fine-grained PAT, and finally... someone mentioned on StackOverflow that it was the git version that was oudated. So, SourceTree has an outdated embedded git, even on the latest version. Wtf?! Anyway, so I let it choose system git (which uses the latest git version).

And now it works!

Haaaaaaaaaaaaaaaaaaaaaa.

Comments
  • 3
    I stopped using SourceTree a long time ago because it became more and more a victim of enshittification.

    I recommend Fork which is similar but better in every aspect.
  • 2
    I think using that such tools is making you complex shit. I use only cli and keep it simple. Using only the basic commands and just frequent rebase if it's within company. That's all. If you need such visual tool, something else goes not OK. Pull pull pull.
  • 2
    @tamagotchi have you seen the image of the git graph that I posted in a rant recently?
    I need that shit.
  • 2
    Here it is again
  • 2
    GitKraken. sourceTree is 💩
  • 1
    @Lensflare yes, and it's confusing. Don't do that :p
  • 2
    @tamagotchi oh, I’m not doing that. I just need to deal with that.
  • 2
    @Lensflare you should never look further than your cli. It's like life, don't look further than your village. It's horrible there. At home everything is whimsical.
  • 2
    @whimsical I just witnessed the exact second in that you have changed your name.

    What are you doing? 😅
  • 3
    @Lensflare if someone asks me if I'm AI. I can say I'm whimsical 😁
  • 1
    upvote for song

    also correct on CLI better. KISS. keep it simple, stupid.
  • 0
    Yup, learned the git cli and never needed tools again. The 4 commands, clone, pull, commit and push; you'll never need anything else for the rest of the 90% of your dev work. I've heard GitKraken recommended before as well.
  • 2
    @BordedDev At my previous job we needed rebase and we also needed to do release management every month, in addition to deploying the app to the cloud under CodeEngine and Kubernetes. Things.. are just not that simple sometimes. Then, depending on which team you worked for, some leads liked rebase, some liked the classic merge. And.. to top it all off, sometimes a team member messed up with the branches and we needed to cherrypick and... yeah.
  • 1
    @CaptainRant personally I don’t give a shit about rebase or not.
    But I need a visual representation of the branch graphs to do things like you mentioned. Cherry picking, fixing commits, etc.
    I don’t really want to fuck around with the cli when I have gui tools like Fork.

    It‘s like with the file system. Why would I want to use cd/ls/mkdir when I have a gui file explorer?
    I’m not a masochist.
Add Comment