{"id":63435,"date":"2022-04-06T09:00:47","date_gmt":"2022-04-06T09:00:47","guid":{"rendered":"https:\/\/www.cryptocabaret.com\/?p=63435"},"modified":"2022-04-06T09:00:47","modified_gmt":"2022-04-06T09:00:47","slug":"make-your-own-git-subcommands","status":"publish","type":"post","link":"https:\/\/www.cryptocabaret.com\/?p=63435","title":{"rendered":"Make your own Git subcommands"},"content":{"rendered":"

Make your own Git subcommands<\/span>
\nSeth Kenlon<\/a><\/span>
\nWed, 04\/06\/2022 – 03:00<\/span><\/p>\n

\n
Up<\/div>\n
Register<\/a> or Login<\/a> to like.<\/div>\n<\/div>\n
\n

Git is pretty famous for having lots of subcommands, like clone<\/code>, init<\/code>, add<\/code>, mv<\/code>, restore<\/code>, bisect<\/code>, blame<\/code>, show<\/code>, rebase<\/code>, and many more. In a previous article, I wrote about the very useful rev-parse subcommand<\/a> for Git. Even with all of these subcommands available, users still come up with functions to improve their Git experience. While you’re free to create Git-related commands and run them as scripts, it’s easy to make your own custom Git subcommands. You can even integrate them with Git through rev-parse<\/code>.<\/p>\n<\/p>\n

\n
More on Git<\/div>\n
\n
What is Git?<\/a><\/div>\n
Git cheat sheet<\/a><\/div>\n
Markdown cheat sheet<\/a><\/div>\n
New Git articles<\/a><\/div>\n<\/p><\/div>\n<\/p><\/div>\n

Create a simple Git script<\/h2>\n

A script that integrates with Git can be as complex as you need it to be, or it can be short and straightforward.<\/p>\n

As a simple example, assume you’ve created a script that gathers the file names of your latest commit and places them into a file called latest.txt<\/code>. You use this script after every commit for reporting purposes, and you’ve decided it would be handy to be able to run the script as if it were a built-in feature of Git, for instance, with the command git report<\/code>.<\/p>\n

Currently, running git report<\/code> renders this error:<\/p>\n

\n
$ git<\/span> report
\ngit: 'report'<\/span> is not a git<\/span> command. See 'git --help'<\/span>.

\nThe most similar command<\/span> is
\n\u00a0 \u00a0 \u00a0 \u00a0 bugreport<\/div><\/div><\/pre>\n
Here’s the script that generates your report:<\/p>\n
\n
#!\/bin\/sh<\/span>

TOP<\/span>=$(<\/span>git rev-parse<\/span> --show-toplevel)<\/span>
HASH<\/span>=$(<\/span>git log<\/span> --pretty<\/span>=format:'%h'<\/span> -n<\/span> 1<\/span>)<\/span>

mkdir<\/span> \"${TOP}<\/span>\"<\/span>\/<\/span>reports ||<\/span> true<\/span>

git diff-tree<\/span> 
--no-commit-id<\/span> --name-only<\/span> 
-r<\/span> HEAD ><\/span> \"${TOP}<\/span>\"<\/span>\/<\/span>reports\/<\/span>$HASH<\/span><\/div><\/div><\/pre>\n
Save this file as git-report.sh<\/code> somewhere in your PATH<\/a>.<\/p>\n
You’re not going to run this script directly, so do include the .sh<\/code> extension in the name. Make the script executable:<\/p>\n
\n$ <\/span>chmod<\/span> +x git-report.sh<\/code><\/span><\/pre>\n
Create the front-end command<\/h2>\n
You can force Git to run git report<\/code> through rev-parse<\/code> and launch your git-report.sh<\/code> script instead of returning an error. Here’s the script:<\/p>\n
\n
#!\/bin\/sh<\/span>

\ngit-report.sh<\/div><\/div><\/pre>\n
Save this file as git-report<\/code> (do not use a .sh<\/code> file extension) somewhere on your PATH. Make the script executable:<\/p>\n
\n$ <\/span>chmod<\/span> +x git-report<\/code><\/span><\/pre>\n
Running your custom Git command<\/h2>\n
Now test it out. First, create the infrastructure and some sample data:<\/p>\n
\n
$ mkdir<\/span> myproject ; cd<\/span> !<\/span>$
\n$ git init<\/span>
\n$ echo<\/span> \"foo\"<\/span> ><\/span> hello.txt
\n$ git add<\/span> hello.txt
\n$ git commit<\/span> -m<\/span> 'first file'<\/span>
\n$ git<\/span> report<\/div><\/div><\/pre>\n
Look inside the reports<\/code> directory to see a record of your latest commit:<\/p>\n
\n
$ cat<\/span> reports\/<\/span>2e3efd8
\nhello.txt<\/div><\/div><\/pre>\n
Pass arguments to your script<\/h2>\n
You can pass arguments through rev-parse<\/code>, too. I help maintain a Git subcommand called Git-portal<\/a>, which helps manage large multimedia files associated with a Git repository.<\/p>\n
It’s a little like Git LFS or Git Annex, except without the overhead of versioning the actual media files. (The symlinks to the files are kept under version control, but the contents of the files are treated independently, which is useful in scenarios where the artistic process is distinct from the development process.)<\/p>\n
To integrate Git-portal with Git as a subcommand, I use a simple front-end shell script, which in turn invokes rev-parse<\/code> for literal parsing.<\/p>\n
The example script provided in this article can’t take any parameters, but the actual Git scripts I write almost always do. Here’s how arguments are passed, for example, to Git-portal:<\/p>\n
\n
#!\/bin\/sh<\/span>

ARG<\/span>=$(<\/span>git rev-parse<\/span> --sq-quote<\/span> \"$@\"<\/span>)<\/span>
CMD<\/span>=\"git-portal.sh $ARG<\/span>\"<\/span>
eval<\/span> \"$CMD<\/span>\"<\/span><\/div><\/div><\/pre>\n
The --sq-quote<\/code> option quotes all arguments following git portal<\/code> and includes them as new parameters for git-portal.sh<\/code>, which is the script with all the useful functions in it. A new command is assembled into the CMD<\/code> variable, and then that variable is evaluated and executed.<\/p>\n
Here’s a simple example you can run. It’s a modified version of a script I use to resize and apply accurate copyright (or copyleft, as the case may be) EXIF data to images for a flat-file CMS I use Git to manage.<\/p>\n
This is a simplified example, and there’s no good reason for this script to be a Git subcommand, but it’s demonstrative. You can use your imagination to find ways to expand it to use Git functions.<\/p>\n
Call this file git-imager.sh<\/code>:<\/p>\n
\n
#!\/bin\/sh<\/span>
## Requires<\/span>
# GNU Bash<\/span>
# exiftool (sometimes packaged as perl-Image-exiftool)<\/span>
# Image Magick<\/span>

PIC<\/span>=\"${1}<\/span>\"<\/span>
COPY<\/span>=\"-Copyright\"<\/span>
LEFT<\/span>=\"${2}<\/span>\"<\/span>

\nmogrify -geometry<\/span> 512<\/span>^x512 -gravity<\/span> Center 
\n\u00a0 \u00a0 \u00a0 \u00a0 -crop<\/span> 512x512+0<\/span>+0<\/span> \"${1}<\/span>\"<\/span>

\nexiftool -Copyright<\/span>=\"${2}<\/span>\"<\/span> \"${1}<\/span>\"<\/span><\/div><\/div><\/pre>\n
The front-end script for Git integration passes all parameters (the file name and the license) through to the git-imager.sh<\/code> script.<\/p>\n
\n
#!\/bin\/sh<\/span>

ARG<\/span>=$(<\/span>git rev-parse<\/span> --sq-quote<\/span> \"$@\"<\/span>)<\/span>
CMD<\/span>=\"git-imager.sh $ARG<\/span>\"<\/span>
eval<\/span> \"$CMD<\/span>\"<\/span><\/div><\/div><\/pre>\n
Try it out:<\/p>\n
\n
$ git<\/span> imager logo.jpg \"Tux CC BY-SA\"<\/span>
\n\u00a01<\/span> image files updated<\/div><\/div><\/pre>\n
Easy Git customization<\/h2>\n
Creating your own Git subcommand makes your custom scripts feel like natural components of Git. For users, it makes the new subcommands easy to remember, and it helps your subcommands integrate into the rest of everyone’s Git workflow.<\/p>\n<\/div>\n
\n
Creating your own Git subcommand makes your custom scripts feel like natural components of Git.<\/p>\n<\/div>\n
\n
\n
  \"Woman<\/div>\n
Image by: <\/span><\/p>\n
Ray Smith<\/p>\n<\/div>\n<\/article>\n<\/div>\n
\n
Git<\/a><\/div>\n<\/p><\/div>\n
What to read next<\/div>\n

\n        \"Creative<\/a>This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.<\/div>\n
\n
\n
Register<\/a> or Login<\/a> to post a comment.<\/div>\n<\/p><\/div>\n<\/section>\n
Powered by WPeMatico<\/a><\/small><\/p>\n","protected":false},"excerpt":{"rendered":"
Make your own Git subcommands Seth Kenlon Wed, 04\/06\/2022 – 03:00 Up Register or Login to like. Git is pretty famous for having lots of subcommands, like clone, init, add, mv, restore, bisect, blame, show, rebase, and many more. In a previous article, I wrote about the very useful rev-parse subcommand for Git. Even with […]<\/p>\n","protected":false},"author":1,"featured_media":63436,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[307],"tags":[],"class_list":["post-63435","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-open-source"],"_links":{"self":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts\/63435","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=63435"}],"version-history":[{"count":0,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts\/63435\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/media\/63436"}],"wp:attachment":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=63435"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=63435"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=63435"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}