3 ms·
For workflow reviews I tend to just push to GitHub and then use it's review diff when making PRs to catch anything I may have missed (typos usually) Ah I do us
by Sleaker 3y ago
For workflow reviews I tend to just push to GitHub and then use it's review diff when making PRs to catch anything I may have missed (typos usually)
Ah I do use git blame sometimes but it's builtin to the ide so I get it while editing code live. I guess this is the biggest difference I have with not wanting a gitgui, any of those ops I feel like I can get with my ide.
- aulin 3y agoSure, magit is in some sense "getting it with the ide". Not sure how advanced is blame in other editors, it's not just blame annotation, is being able to navigate the history of a line just jumping from one change to the previous and back. It's incredibly helpful with large code bases to understand how some code evolved and why it's implemented like that. Another great magit feature is being able to open a file from any git revision. Like you want to copy some line from a file that's being long removed you can just call magit-find-file on a revision that still has it, open it in buffer, copy what you want etc.
- Lio 3y agoI agree, navigating blame history is incredibly useful, if only to save you from asking the wrong person about a particular change. Vim's Fugitive[1] can do this and also in Textmate to. So I would hope that most editor git plugins can. 1. https://github.com/tpope/vim-fugitive https://github.com/tpope/vim-fugitive