Maybe it is just because I live in the command line anyways (enough so that I have iTerm setup to just pop up from the bottom of my screen with a keyboard command) that I just feel more comfortable with the command line? After the creation of the branch I am back to my cli. but even using that just gives me a weird disconnect with what is actually happening that it doesn't feel right. I have started to dip my toes into it a bit now with the Atlassian integration that can name new branches properly. For me "git status" > "git add XYZ" > "git status" > "git push" are so ingrained in my workflow that I don't get that feedback in any UI I have seen. Outside of that I generally find that any GUI for git just inevitably makes something just opaque enough that I don't really know for sure what I am about to commit or where I am pushing too. Personally the only GUI stuff I find useful are the features that are already part of VSCode (live showing what I have changed or doing a diff). The UI does look really good, but I do wonder how much of the dev community uses a GUI vs just sticking in the command line? If you need to do some git surgery over high-latency SSH, then it's hard to beat Emacs with TRAMP. It's the same reason I'm learning vc.el and magit too. Then I can choose and/or recommend it for different situations. I will check out Fork regardless, because it's good to know what's out there and what are the different set of tradeoffs it choose. It also sprinkles your repo with projects files under a. Now the cost of all this convenience is that you need to download hundreds of megabytes and IntelliJ CE has a substantial startup time and memory consumption, since it indexes your code. It's a significant reduction in mental overhead, imho. You don't know what are you missing out on, until you experience it! If you need to do something more involved, like refactoring or jump to definition, u can always get to the source code with F4 from the commit dialog or from within any commit context. You can auto-complete code, look up docs or the source code of function definitions, even in JAR files, without leaving the context of the commit dialog. It also has a magic-wand icon, which seems to resolve 95% of conflicts automatically and correctly, presumably doing something based on common ancestor commits.īUT what makes both this 3-way merge interface AND the commit interface really great, is the ability to edit in-place, with all your custom keybindings, syntax highlighting, linting and code intelligence tools! The sticking point for me is how well it deals with the 3-way resolution of merge conflicts. The JetBrains IDEs are cross-platform, including Linux and cross architecture, including ARM, because the JVM/JDK is cross-arch. IntelliJ Community Edition is even free and open-source, so for Java coding it's perfect, but pretty good for Clojure, Python, PHP too. My choice is the VCS client in JetBrains IDEs, like IntelliJ, WebStorm, P圜harm etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |