gadiener

#!/bin/bash

# How to run: `./backup_cluster.sh | tee export-$(date +%s).log`

set -e

if [ -n "${DEBUG}" ]; then
  set -x
fi

mauromarano

#!/bin/bash

###########################################################################
# AUTHOR: Mauro Marano
# SITE: mauromarano.it/com
#  Questo script serve per tenere organizzato il desktop
#  Una volta impostate le variabili lui andrà a creare delle cartelle
#  Per ogni tipo di file specificato.
#  La cosa migliore è farlo girare con un cronjob.
#  crontab -e 

andykuszyk

#Useful Git Hooks

Below are a couple of simple git hooks that can be useful for controlling and formatting commits. These are generally re-hashes of other people's ideas, so I've credited these as appropriate.

Git Hooks

A git hook is a script that lives in your .git/hooks directory. The scripts are invoked when certain events occur within your repo, such as make a commit or pushing changes. Hooks can be used to automate and augment basic actions within your repos.

##Include an issue number in your commit message To amend your commit messages after they have been submitted, you'll need a commit-msg hook. I borrowed most of these ideas from @monkseal. This hook assumes that your issue numbers are formatted into you branch names in a way that you can extract using a regex.

rponte

# The command finds the most recent tag that is reachable from a commit.
# If the tag points to the commit, then only the tag is shown.
# Otherwise, it suffixes the tag name with the number of additional commits on top of the tagged object 
# and the abbreviated object name of the most recent commit.
git describe

# With --abbrev set to 0, the command can be used to find the closest tagname without any suffix:
git describe --abbrev=0

# other examples