ToolGit: A collection of scripts that extend Git with various sub-commands

Post by keybored » Sun, Nov 03, 2024, 8:53 PM UTC

nextaccountic wrote: post #22

henshao wrote: post #14

These should be aliases in your git config. git config --global alias. I'm really trying to understand, and not to be too negative. I get coming up with a solution to a problem, and finding it neat locally. But before posting to HN, one might realize that these solutions that git provides existing tools for is better than maintaining this. I'm also confused by all the comments just blindly commenting in the affirmati…

The trouble is that git aliases aren't composable and you can't install them. Each installation has its own aliases. If you are in a new machine you must define the aliases yourself. This also makes git aliases have poor discoverability. Compare this with another tool that lets people extend its own command, cargo. You can do cargo install and then run cargo .

Post by secondcoming » Sun, Nov 03, 2024, 9:43 PM UTC

porridgeraisin wrote: post #2

https://gist.github.com/romainl/a3ddb1d08764b93183260f8cdf0f... This script in your path means that after you say pull code and have merge conflicts, "git jump" will open vim with the quickfix list populated with the locations of the conflicts.

Post by henshao » Sun, Nov 03, 2024, 10:22 PM UTC

n4r9 wrote: post #24

henshao wrote: post #14

These should be aliases in your git config. git config --global alias. I'm really trying to understand, and not to be too negative. I get coming up with a solution to a problem, and finding it neat locally. But before posting to HN, one might realize that these solutions that git provides existing tools for is better than maintaining this. I'm also confused by all the comments just blindly commenting in the affirmati…

What would the alias command be for git-delete-gone-branches ? EDIT: I saw your other comment (incorrectly) claiming that git remote prune origin will do the job. I don't know of any git trickery that can do the job. And believe me I'd love it if there was something.

    git fetch -p && git branch -vv | awk '/: gone]/{print $1}' | xargs git branch -d

Post by henshao » Sun, Nov 03, 2024, 10:31 PM UTC

ahmetsait wrote: post #29

henshao wrote: post #14

These should be aliases in your git config. git config --global alias. I'm really trying to understand, and not to be too negative. I get coming up with a solution to a problem, and finding it neat locally. But before posting to HN, one might realize that these solutions that git provides existing tools for is better than maintaining this. I'm also confused by all the comments just blindly commenting in the affirmati…

Hi! Author here. Some of these can indeed be an alias, others.. not so much. `git-root` for example is more-or-less a one-liner, meanwhile `git-mode-restore` is a ~840 loc python script. I do use git aliases but trying to do anything non-trivial in them seems rather counter-productive so I'm confused about everyone suggesting it :P

    git config core.fileMode false

Post by bloopernova » Sun, Nov 03, 2024, 10:49 PM UTC

listeria wrote: post #38

bloopernova wrote: post #13

Some of my git aliases might be useful to folks here (I post them from time to time on git threads) Time to share my gitconfig aliases again :D lol = !git --no-pager log --graph --decorate --abbrev-commit --all --date=local -25 --pretty=short sw = !git checkout $(git branch -a --format '%(refname:short)' | sed 's~origin/~~' | sort | uniq | fzf) lc = !git rev-parse HEAD rb = !git for-each-ref --sort=-committerdate ref…

I see that you're using --print0 and -0 for your "git fza" alias, it might be useful to add -z to the git-ls-files invocation and --read0 to fzf.