-
Semi-related, I recently discovered https://github.com/dandavison/delta: A syntax-highlighting pager for git, diff, and grep output
It appears to enable choosing between unified and split views for each of those tools.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
I was curious to see if anyone tried leveraging an LLM for summarizing diffs, and of course they have. An example here: https://github.com/anc95/ChatGPT-CodeReview/pull/21
It seems to me it misses the mark a little -- the text is so verbose, it's easier to read the code itself.
-
-
Poorly worded, granted. We use some internal tooling to make things work, but the concepts are generic git and $forge.
Push a comment: I'll make a hand-wavy suggested edit, then the vim mapping basically performs a ":`<,`>w !curl". If you only used GitHub, something like "gh pr comment"Ā¹ could perform a similar-ish role.
Pull comments: We automate merges so that PR text(including replies) are available in the repo. For the general discussion they're attached as notesĀ², and for code comments(including --fixup commits) they're processed to assign the correct attribution via trailersĀ³ to the original commit at merge time. Most of the attribution functionality could be re-implemented with "git rebase --autosquash" and by providing a "git interpret-trailers" wrapper as EDITOR.
Ā¹ https://cli.github.com/
Ā² https://git-scm.com/docs/git-notes
Ā³ https://git-scm.com/docs/git-interpret-trailers
