Modify the Git Hooks structure, to enable chain calls and external/tracked hook files
Shell Makefile
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
snap
src/usr/bin
.gitignore
LICENSE
Makefile
README.md
composer.json

README.md

githooks

Tiny framework to help you working in your git hooks.

Description

Utility used to enable some particular capabilities when using git hooks, as chaining support and load of versioned hook files inside the repo. Your defined hooks will be preserved, but will live in a more appropriate place.

Folder Structure

It's really simple, aimed to enable program distribution under different formats.

  • src: contains all the real code on the solution.
  • composer: configurations to offer this package in composer.
  • snap: configurations to create a snap package on the project.
  • Makefile: configurations to install the package but using the ubiquitous make tool.

REQUIREMENTS

In general in any modern GNU/Linux, installing src files and folders in the correct place will be enough; even better, for Ubuntu there's a SNAP package available for you to install, just look for githooks in the snaps store..

For OS X, you'll need to get the composer package plus some adjustments to your system; all can be done by using Homebrew (tested in a system using that). Next the reqs plus some installation guides:

  • Git (of course) OS X - No problem by using the default git version.
  • Bash >=4 OS X - Follow this guide http://johndjameson.com/blog/updating-your-shell-with-homebrew/ to enable it.
  • Coreutils >=8 OS X - brew install coreutils to enable it.
  • getopt >=1.1.6 OS X - brew install gnu-getopt to enable it.
  • Homebrew only for OS X.

Important for OS X to mention there’s no need to install Homebrew packages with --default-names options, as the script internally deals with that, when available.

NOTE: Maybe there are some clever ways to overcome the OS limitations, but it seems easier, and in general good for the OS, to have more up-to-date packages, when available. In any case, fixes are welcome.

INSTALL (it's quick)

Install it (via SNAP or composer). If used SNAP, you're done, enjoy.

If used composer, you'll have to create a link to the githooks script (inside src/usr/bin/) to a coherent place for your proyect or addapt your $PATH to include this new location. IMPORTANT, beware you don't have both approaches installed at the same time.

By default a folder named trackedhooks (living next to the .git dir) will be used as reference for the hooks that will travel with your repo. In case you want to set something different, be sure to adapt the external vars, as defined at the end of this doc.

Then, run githooks --init, and enjoy (again 😛).

See below for more command options.

GENERATED STRUCTURE

By default git only handles one hook file per repo. With this solution, you'll be able to add any amount of hook files, that will be called sequentially.

And this is the new structure:


.git/hooks/
 │
 ├── hook files
 ├── hook names folder.d/
 │    ├── script
 │    └── ...
 ├── trackedhooks/
 │    └── hook names folder.d/
 │        ├── script
 │        └── ...
 └── _.sh

Can look a bit intimidating, but actually it's really simple.

  • hook files: are all the Active hook files (use the name of the hook as filename). This is the normal git way of handling hook files, but here, in order to support chaining, they are only symlinks (ln -s) that points to "_.sh" (more on this, later).

  • hook names folder.d/: folders that contains all files to be called when a hook is executed. For instance, if hook "commit-msg" is Active, a folder named "commit-msg.d" must exist. Files inside it will be called sequentially, using alphanumeric sort, so you state their execution order.

  • trackedhooks/: link that points to the folder with all the hooks that will be tracked, to make them available here. Inner structure must follow the one for "hook names folder.d/".

  • _.sh: special file used to concentrate all git hooks activity. Remember, all files in "hook files" are links to this one? Well, that's because this is used to dispatch the execution to the other ones, under "hook names folder.d/" and/or "trackedhooks/", using the hook name as key. That's the reason folders must use the hook name as part of their names. This file is created by using this script.

This script can be used to create and handle this structure, so you only worry about creating the hook process you want.

HOW TO USE THIS SCRIPT

You can perform several operations. You'll see all of them share the option -y, that's used to reply yes to any prompted question. And the options are:

  • --help/-h. General help on how to use the script.

  • --status/-s [<hook-name>] [-ty] (default). General status info with all active hooks and paths to their files. If no options defined, it will print all hooks info, otherwise only those ones that make a match. '-t' means look only in trackedhooks/ folder. The status report also includes info about current structure.

  • --init [-y]. Creates the basic structure, as defined above. The next is performed:

    • Remove+Add the _.sh script.
    • Remove+Add the linked trackedhooks/ folder.
    • Transform all active hook files into the new chaining version.
  • --destroy [-y]. Reverts the creation of the new structure. New files and folders will be removed. Active hooks will be kept as active, but in case more than one file has been detected, only the 00default will be used. Other files will be left in their respective folders and won't be removed to preserve data. "trackedhooks/" folder and "_.sh" script will be removed.

  • --on/-1 <hook-name> [-y]. Activate a given hook given the hook type. It just deals with the link file, the one that points to the _.sh script.

  • --off/-0 <hook-name> [-y]. Deactivate a given hook given the hook type. It just deals with the link file, the one that points to the _.sh script.

  • --add/-a <hook-name> <file-name> [-ty] [--do-edit]. Creates a new hook file, given the hook type and the file name. On collision, it will ask before proceed. The option '-t' means create it in the "trackedhooks/" folder, whenever possible. When no options given, the command will respond with an error and possible options. On success, the file wll be created/recreated and your favorite editor opened, if the option '--do-edit' is set too.

  • --edit/-e <hook-name> <file-name> [-ty] [--do-add]. Lets you edit a given hook file, given the hook type and the file name. It uses the favorite editor set. The option '-t' means search in the "trackedhooks/" folder, whenever possible. When no options given, the command will respond with an error and possible options. In case the file does not exist, you can create it there by using the option --do-add.

  • --delete/-d <hook-name> <file-name> [-ty]. Delete a given hook file, given the hook type and the file name. The option '-t' means search in the "trackedhooks/" folder, whenever possible. When no options given, the command will respond with an error and possible options.

EXPORTED VARIABLES

There are some vars you can set to alter some settings. Those are:

  • TRACKEDHOOKS_FOLDER. Used to set the path of the "trackedhooks/" folder to something custom. It can specify deeper levels if you include '/' chars in the name. It's always refered in base to the main repo folder (the one that contains .git folder).

  • TRIGGERSCRIPT_FILENAME. Used to change the name of the generated triggering script (default _.sh).

  • DEFAULT_EXTENSION. Used to change extension used for already existing scripts in local when moved to the new location (default 00default).

  • NO_COLORS. Used to deactivate colored messages.

Composer

Check the "composer.json" file. That's used to publish this as a composer package in https://packagist.org/

Makefile

Clone the project and, inside of it, run:

sudo make install

Done! For upgrades, simply clone the project again and run the previous command again.

To remove simply run sudo make uninstall.

Snap Package

Check snap folder with all configuration information ready to build a snap package. More info about snaps here https://docs.snapcraft.io/snaps/intro.

Commands to trigger package creation can be run from this project's root level.

TODO:

  • Check how to create a cleaner snap package. So far, when run snapcraft cleanbuild command, everything goes great, but there's a .bz2 file inside the created snap that has everything this repo has, even .git folder, and that's how that's published. No Bueno!

Ubuntu PPA (legacy)

THIS HAS BEEN DEPRECATED, NO LONGER CREATING .deb PACKAGES.
Left this here for future reference.

You can find the package as a PPA here https://launchpad.net/~dalguete/+archive/ubuntu/githooks

Sidenote: About My Experience Creating .deb Packages Plus Ubuntu's PPA

http://dalguete.github.io/#about-my-experiences-creating-deb-packages-plus-ubuntus-ppa