5 ms·
GitHub Desktop 3.2: Preview your pull request
- hnbad 4y agoStill no support for WSL and VSCode Remote with WSL tho, sadly.
- LilBytes 4y agoAre there any tools you'd recommend for WSL2? SourceTree has the same problems. I'm fond of just using the CLI but I'd like to be able to recommend a UI tool for other Devs. Haven't found one that works for Windows and WSL2 together.
- sander1095 4y agohttps://www.gitkraken.com/blog/wsl2-and-gitkraken-client https://www.gitkraken.com/blog/wsl2-and-gitkraken-client might fit your needs
- LilBytes 4y agoPerfect, thank you.
- nusaru 4y agoSo basically, now we can do `git diff master` in a GUI. Hooray, I guess.
- netr0ute 4y agoWhy use nano when vi works just fine?
- nusaru 4y agoI mean, if vi is what you prefer, more power to you.
- nkozyra 4y agoI'm assuming the point was power tools versus very basic and more approachable ones, and I think there's a place for both. To use this example, I use vim most of the time but sometimes I jump into nano to do a quick edit on something. I don't love most of the GUI tools for git, but I use Sourcetree for 10,000 ft visualization and can't really parse CLI git --log graphs, even if they're heavily decorated.
- 2OEH8eoCRo0 4y agoYeah, what we really need is yet another electron app.
- randyrand 4y agoThe UI for the diff is actually useful though. Much easier to read and browse than a terminal.
- nusaru 4y agoYou're not wrong. Personally, I just used GitHub's web UI to preview my PRs, but I suppose having a local GUI makes it easier to amend commits and not have to force push changes.
- 2OEH8eoCRo0 4y agoElectron apps eat my ram and web UIs run like shit when backed by a large private instance.
- steve_adams_86 4y agoIt was mentioned elsewhere but you might find Sublime Merge to be useful; it's not based on Electron, it's very fast, and it makes working with various git workflows a lot nicer (to me, at least).
- david2ndaccount 4y agoYou can use `git difftool` to view the diff in your tool of choice (including gui editors).
- u801e 4y agoI've found piping the output of git diff to my editor makes it much easier to browse compared to using the UI. For instance, searching for a particular file or line of code it much easier in the editor compared to the browser.
- ripplefringe 4y agoI use Github Desktop. One thing I do like a lot is that the diff I see is exactly what my code reviewers will see. Personally, I spend a lot of time reviewing other's code ad also going through my own PR's in Github. I'm very familiar with that view. I think it helps my brain that I use the same diff view when I'm working locally and when I'm reviewing code on Github.
- u801e 4y ago>> So basically, now we can do `git diff master` in a GUI. > One thing I do like a lot is that the diff I see is exactly what my code reviewers will see. What will they see in the diff that you can see using Github Desktop that you wouldn't see by running git diff master?
- ripplefringe 4y agoColors and fonts especially. After ten years my brain is fast at reading a GitHub diff. It’s pretty slow at reading a terminal diff because I don’t do it very much.
- u801e 4y agoPresumably most people use an editor or IDE for coding and it's likely that editor or IDE could also be used to display diffs, so I don't really see colors or fonts being an issue. The IDE or editor could also be configured to use colors and fonts similar to what's used in Github. For example, vim has a colorscheme[1] that's similar to what Github offers. [1] https://github.com/cormacrelf/vim-colors-github https://github.com/cormacrelf/vim-colors-github
- nixpulvis 4y agoGitHub desktop/mobile apps have been the worst thing to happen to GH since / along with the acquisition. The website is being neglected, (especially on mobile) which is the primary value the service has for me. If I have `git` I really don't need GitHub except to view comments. Ironically, notifications and comment management is still pretty bad. Don't get me wrong, I still think GitHub is the best at what they do, but like many incumbents, I feel like they are losing a bit of what makes them so great. Polish up the features you have, we don't need endless feature releases, we need smooth features we know and love.
- jerpint 4y agoIm a heavy user of GitHub website and I find it doesn’t stop improving
- thrashh 4y agoAs someone who has built GUI wrappers for perfectly working tools, it’s because support is a nightmare. There’s a subset of your users who aren’t going to invest in learning your existing tools but you still want them to use your product. You can’t write more documentation because the more documentation there is, the less people will read it. You can’t tell them to ask for support because they’ll just flood you and eventually give up. So you build a GUI for these users and they’re happy and you’re happy. Your expert users won’t understand, will complain that you’re wasting your time, but that’s a price worth paying.
- slugiscool99 4y agoThe worse thing to happen to GH? Really? Using git on the command line can be hard to learn and unintuitive for people - the desktop client makes things easier and that's a good thing (kind of like how the GUI made computers accessible to more people and ended up benefiting everyone in software...)
- tracker1 4y agoTBH, I felt the same way for a while... but I found that I really only need to actually remember a handful of things.. git add, git commit, git pull --rebase, and the git rebase -i HEAD~N Other than those, when I need something I don't typically use, I have google. And most of those instances where it's not one of the commands above, the UI is usually pretty bad anyway. I do like the preiew/diff in VS Code a lot though on the git tab. I do wish there was a way to post-operate on the most recent commit (uncommit) via the gui though. I tend to work in a branch, regularly squashing and rebasing against upstream branch... then would prefer to be able to (via gui) uncommit the most recent commit, just so I can preview/edit a final pass at once. That is about the only workflow that I sometimes want/need that isn't really in the box, or otherwise more of a pain in the UI anyway.
- coldblues 4y agoSublime Merge is still the best option so far (not Electron)
- steve_adams_86 4y agoAbsolutely, what an excellent tool. One of those one-time purchases I almost wish was a subscription so I can be sure the team keeps working on it. I actually understand git better because of Merge. It's great because it provides a great interface into git, but it doesn't _hide_ git from you; it explains it quite a well. I suppose a newcomer to git might find Merge intimidating, but for anyone with a bit of experience I think it's quite an awesome power tool with a rare balance of handy abstraction and transparency around git itself.
- EduardoBautista 4y agoLicenses are valid for three years of updates. So, it is a subscription, just a very long one with a fallback version when the subscription ends.
- nkozyra 4y agoThen the software isn't a subscription, the updates are. This is also kind of how the Jetbrains stuff works and it's far less user-hostile than making someone pay in perpetuity to simply use the software.
- steve_adams_86 4y agoI can't imagine the Sublime Merge version I have today won't still be super useful once my license expires, so for a lot of people, buying a new copy might not seem particularly compelling. It's also so cheap (or it was when I bought it) that it's waaayyyyy less expensive than any 3 year subscription I've ever seen – something like $2/month.
- calvinmorrison 4y agoPeople on my team use it. I guess it's fine, but when they get stuck with git (a-la locate git.txt and call the number listed on it), I am sort of at a loss of what they did to get where they are. At least with git commands you can sort of see how they got there. Just my 2c
- heydenberk 4y agoIf you get a lot of value out of the pull request view, you might enjoy adding partial committing to your workflow. Rather than committing entire directories or folders at a time, you can page chunk by chunk through uncommitted changes, committing only the ones you select. You'll easily spot those stray logging statements you don't want to commit. (You can also discard chunk at a time by using partial checkout/restore.) If you have, for example, two pairs of backend/frontend changes that you want to commit logically rather than simply according to their directory structure, partial committing is handy. It's just `git commit -p` (and `git checkout -p`). It's not exactly a deep cut, but I encourage people who are familiar but don't use it to give it a try.
- steve_adams_86 4y agoInteresting, I knew of `git add -p` (which I then use to `git commit -m ...`, but it looks like I could add all changes and _then_ decide what to commit. I think I'd still use `add -p` (I like being thorough), but I like that I can add all at once and then make partial commits based on specific change sets. Thanks for pointing this out, I feel like git is the thing I should know best by now yet I'm missing so much of what it can do. It's great to see others' workflows.
- tracker1 4y agoI've tended to have a similar workflow... but since I use VS Code mostly, then I do use the git tab a lot for previewing changes before committing them. Other than that, I've mostly avoided using any GUI for git, mostly because I find it annoying. I'll say that the Github client and the VS Code integrations for Github have come a long way all the same for those that use and like them.
- brasic 4y agoMy favorite git workflow extension is `git commit --fixup SHA` combined with `git rebase -i --autosquash` to create targeted retroactive amendments. Kind of like `commit --amend that can target more than just the last commit. I wrote https://github.com/brasic/fixdown https://github.com/brasic/fixdown to make this easier to use.
- _hao 4y agoSeems to compare quite poorly to GitKraken (which I realize is paid, but it's really good).
- nerdyadventurer 4y agoMay I know, in which cases desktop apps becomes beneficial over web apps in general?
- bdcravens 4y agoWhen you need to interact with resources on the user's machine as any part of the workflow.
- amir734jj 4y agoI haven't found a need to use graphical git user interface. I work daily with repositories with millions of lines of code and git cli is good enough.
- chadlavi 4y agoHuh, TIL there's an official GitHub desktop app