I've been using Fork: https://git-fork.com/ because of its 2 primary advantages over SourceTree: • Dark mode • Tabs
[deleted]
Show HN: I made a tool that made me faster at Git
61–70 of 235 posts
Re: Show HN: I made a tool that made me faster at Git
#62If you're an emacs user, I can't recommend magit [1] enough. I was a diehard CLI user and had flags and aliases out the wazoo, and it was still a step change in usabilty and power for me. Staging hunks, rebasing, and stashing are all vastly easier. Amending or editing a commit is a breeze, and it's tied in to all of the other emacs tools you already use, e.g. org-mode to boot! It's easier to see it in action than exp…
Based on those videos, lazygit looks like it does the same things as magit, but with a little more "chrome" (boxes around lists). How do the two projects compare? Could they be merged, or do they have fundamentally different philosophies?
Re: Show HN: I made a tool that made me faster at Git
#63Earlier quoted context omitted.
this readme really speaks to me
I'm out of the loop. What's the story here? Why are devs sad about Atlassian and Jira?
Honestly, it's just enterprise software. The problems I have with Jira are largely the same problems I have with any software developed exclusively for enterprise customers. Enterprise customers always get what they want, so every piece of enterprise software is a bloated piece of shit that does 900 more things than any sane person should ever want it to do, and nobody gives a shit because the people using the software are rarely the people deciding to buy it.
Re: Show HN: I made a tool that made me faster at Git
#64'Go' question that came up when I tried to build this: How do you build a Go .EXE on Windows that doesn't have any file paths embedded in it?
go build -gcflags=-trimpath=$GOPATH -asmflags=-trimpath=$GOPATH
Re: Show HN: I made a tool that made me faster at Git
#65Earlier quoted context omitted.
Jira is Turing-complete. Let me repeat that. Your ticketing system is Turing-complete. I don't remember where I heard this first, but someone at my company (at least supposedly) proved it once. Jira has managed to grow into such a bloated, complex, incredibly pointless piece of software that I've never met someone who likes it. It's like software design by committee, where every manager involved had some pet project…
it's really not that complex at all...
From my limited experience, Jira workflow at a company reflects the culture. Maybe jira can be a tool to surface organizational defects and deficiencies...
Re: Show HN: I made a tool that made me faster at Git
#66> are YOU tired of typing every git command directly into the terminal
I'm not. Are there many people that are? Is this not just a matter of learning to use shell keybindings effectively? That and aliases does wonders to avoid repetitive typing. Many times I type `git s` (alias for `git status -s`) out of reflex when I really meant to do `ls`.
When I forget to add `-a` to `git ci -m ...` (`ci` being `commit`) and get an error because the index is empty, I just `kF-aa` ( being ) to add it and re-execute. It's muscle memory; I do it before I even realize I did it.
Re: Show HN: I made a tool that made me faster at Git
#67Might be a good opportunity to advertise my git-send bash function / zsh plug-in:
Re: Show HN: I made a tool that made me faster at Git
#68One Git UI that I absolutely love but I rarely see mentioned is GitKraken. It's so nice having a fully cross-platform Git GUI, that's attractive and intuitive.
Re: Show HN: I made a tool that made me faster at Git
#69'Go' question that came up when I tried to build this: How do you build a Go .EXE on Windows that doesn't have any file paths embedded in it?
go build -gcflags=-trimpath=$GOPATH -asmflags=-trimpath=$GOPATH https://stackoverflow.com/a/45302415
Did you try this yourself? Because I already tried it and it didn't work. Remember I said I'm on Windows.
Re: Show HN: I made a tool that made me faster at Git
#70If you're an emacs user, I can't recommend magit [1] enough. I was a diehard CLI user and had flags and aliases out the wazoo, and it was still a step change in usabilty and power for me. Staging hunks, rebasing, and stashing are all vastly easier. Amending or editing a commit is a breeze, and it's tied in to all of the other emacs tools you already use, e.g. org-mode to boot! It's easier to see it in action than exp…
magit is lifechanging -- At this point I open emacs (assuming it isn't already open) just to use magit to manage things.
If you use it daily don't forget to donate to the developer at least once, sprinkle some of that full-time corporate cog money on them.