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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |