![]() ![]() 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. Being able to do something weird like drop or reorder a single commit without fussing with a rebase, or quickly reword the commit message is just…nice.Ĭlearly I’m still conflicted about this, as such, I’m going to use the easiest one which is Fork for now.For years, I've been using Sourcetree as my go-to-tool for all Git related actions and repository management. I don’t think it’s a good enough trade-off yetĮ.g.Juggling commits is better in Gitkraken. ![]() Gitkraken has vastly superior integrations.It’s just not something they’re focussing on at this stage (I have a slightly unusual setup) Conclusion? I did have some issues with Gitkakens one-button oauth solution and submitted a bug. To be fair, Gitkraken isn’t really slow, it’s slower than Fork. Integrations are great, but it doesn’t feel worth juggling PAT’s to make it work. Gitkraken is leaning into some distinguishing features like it’s Terminal, Workspaces, and other integrations which is nice BUT I don’t care as much about that as I do some other things like:įork is massively almost overwhelmingly superior in both of these aspects. The UI differences are there but they’re not significant, and yet I feel like Gitkraken is a bit nicer. That sounds like the correct behaviour, but recently in Fork I ticked “Remove stash after applying” and moved on, but it was remembered the next time which I didn’t want. Perhaps it’s the fact that the defaults and flows mean I get less prompts, and if I set something that ISN’T a default, it’s NOT remembered. It’s defaults fit my workflow quite well, and SOMETHING about it just feels a bit nicer. ![]() Reading all the above “facts”, it feels like I’m leaning towards Gitkraken, and to some extent I am. Sometimes it doesn’t matter what the tool does, it’s more about how it feels.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |