51–60 of 72 posts
Still no support for WSL and VSCode Remote with WSL tho, sadly.
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.
Still no support for WSL and VSCode Remote with WSL tho, sadly.
Are 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.
might fit your needs
If 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/restor…
This functionality is built-in to vim-fugitive and VS Code. In Fugitive, open it with :Git , select the unstaged file then press = . Select the desired range with visual mode, then press s and commit as normal. In VS Code, select a hunk, press Ctrl+P, then type "Stage Selected Range." Repeat this process and commit as normal. Edit: formatting and typo.
If 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/restor…
Earlier quoted context omitted.
For those who want a GUI around this on Mac, https://rowanj.github.io/gitx/ is an incredible secret weapon. You can swipe over a bunch of lines or let the software identify a whole span of contiguous changed lines, click a button, and see just those changes move over from your unstaged to staged changes, then commit exactly what you want. A lot of times people don't even understand how powerful the staging area is; t…
According to this issue[0] there is a newer and maintained version of gitx. [0] https://github.com/rowanj/gitx/issues/481
May I know, in which cases desktop apps becomes beneficial over web apps in general?
GitHub 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, b…
Earlier quoted context omitted.
You can commit line by line within Github Desktop and its a much nicer experience IMO than doing so via CLI. Its much easier to jump around to different files and commit related line changes in a bigger PR than jumping in and out of the patch command.
git gui which you probably already have if you use Linux also has this functionality.
There's a stackoverflow discussion [1] that suggests it was fixed in 2018, but for many years it was a terrible experience that pushed me to use other frontends just for reliable partial staging.
1: https://stackoverflow.com/questions/58133092/git-gui-error-f...
Earlier quoted context omitted.
According to this issue[0] there is a newer and maintained version of gitx. [0] https://github.com/rowanj/gitx/issues/481
https://github.com/gitx/gitx/releases my daily driver in mac