gitscripts - some custom git commands

Written in 2019 by Eliah Kagan <degeneracypressure@gmail.com>. Minor update in 2021.

To the extent possible under law, the author(s) have dedicated all copyright and related and neighboring rights to this software to the public domain worldwide. This software is distributed without any warranty.

You should have received a copy of the CC0 Public Domain Dedication along with this software. If not, see http://creativecommons.org/publicdomain/zero/1.0/.

This repository contains scripts that start with git- and conceptually perform well-defined actions for git.

When installed to a directory listed in $PATH, a script (or other executable) git-X defines a new git command X. Running git X ... calls git-X ....

See BUGS.md for information about known bugs.

Here's a summary of the commands:

git-chmod

This command changes executable permissions for files in the index. Use it like chmod, but specify only +x or -x as the mode. Pass one or more paths after the mode. For example:

git chmod +x foo
git chmod -x bar baz quux

This is mostly useful on Windows (with Git for Windows), together with git-lsx to inspect the permissions (see below). git-chmod is a thin wrapper for git update-index --chmod=.

git-lsx

This command lists files in the Git index with their associated permissions, emphasizing those marked executable (and, in a different style, symlinks) in a manner similar to the effect of ls --color=auto -F.

This is mostly useful on Windows (with Git for Windows). On a Unix-like system, your repositories are presumably on a filesystem that supports Unix-style permissions, so you can usually just use ls -l. Occasionally you might still want to inspect the index rather than your working tree, though.

git-pull-all-branches

This command pulls all branches from the origin remote. Currently it uses origin even if it's not the upstream remote, which should be considered a bug.

I don't plan to add git-push-all. I suspect a substantial fraction of git push-all usages would be mistakes. More important, I have rarely wanted to do that personally.

However, you may want to look at git push --all, which probably does what you want; unlike pull, where --all does not merge to all branches (rather, it fetches from all remotes before merging), with push the --all option does cause git to push all branches.

I renamed this from git-pull-all to git-pull-all-branches in December 2021 to avoid confusion. To do what git pull-all did before, run git pull-all-branches (or rename it back locally if you prefer the old name). If you deploy these scripts and already had git-pull-all, it will not be deleted, so you may want to delete that. Note that this may not require more typing than before, if you have tab completion (type git pull- and press tab immediately after the hyphen).

---

Shell prompt customization is not in this repository. See git_prompt_activate.