![]() ![]() push to origin/develop pull from upstream/develop using the buttons on the top menubar). My question is, is there any way to set a different remote repository in Gitkraken for pushes and pulls? (E.g. I've recently found an Ubuntu machine to develop on, and having found that Sourcetree isn't available for Ubuntu, found Gitkraken as a potential alternative. Maybe it pays out someday.Īnd just because it reads like a paid article: it’s not.I've been working on a Mac using Sourcetree to manage my repositories. Always talk with the companies and let them know what you need. I've talked with Axosoft (the company behind GitKraken) and they have more GitLab support on their board and +1ed it for me. I found out that this context thing really grinds my gears or at least hinders productivity. Now, if I could just bring my contexts down to 1 (!). Great merge conflict editor (no more "mine" and "theirs" □♂️). ![]() I brought my contexts down from three to two and profit from other sweet features like: I'm entitled to have some nice things in life, ok?). I've been under the hood when I started with the terminal for the first couple of years. With the undo feature, I don't have to look up reset commands any more or do hard resets because it's sometimes cumbersome to reverse an action (Yeah yeah, it's good to know what's happening under the hood, I got you. If that doesn't get you off your seat and have you throwing money at this tool, I'll throw in an epic undo/redo feature which lets you reverse and redo actions (I already see the comments, where you complain that you can't take back a commit after you've pushed it. Secondly, I can still stay in my Git tool to see the issues which are assigned to me in Jira, change them, and move them in their workflow. Can we just pause for a second and process this? It doesn't feel like much but go dare and try. Due to a recent change in their pricing structure, I was ready to give it a spin, and oh boy, did this tool go to town (with me).Īfter I learned about some of GitKraken's features, my new (improved) workflow looks like this:įirst of all, I can stay in my Git tool to create merge requests. In conversations with my colleagues, I've heard that some used a different Git client (like GitTower ) and so I stumbled across GitKraken during a Google search. I always thought that this is how it is to code nowadays. ![]() The context switches between these tools were never something that bothered me. To finish a piece of work, I usually have to work with three tools: Sourcetree, GitLab, and Jira (not shown in this picture). Pretty standard, no special things here ✌️. Here's a standard workflow, I usually follow:Īt my work, we use GitLab / GitHub for code management and pipelines and often feature branches to structure the way teams work. To understand why I changed my mind, it might be interesting to understand, how I work. Picture taken from GitKraken's website. It did all I could wish for and I couldn't imagine why someone would pay for a Git client. For years, I've been using Sourcetree as my go-to-tool for all Git related actions and repository management. ![]()
0 Comments
Leave a Reply. |