/hooks/post-unlock.tmpl

 1#!/bin/sh
 2
 3# POST-UNLOCK HOOK
 4#
 5# The post-unlock hook runs after a path is unlocked.  Subversion runs
 6# this hook by invoking a program (script, executable, binary, etc.)
 7# named 'post-unlock' (for which this file is a template) with the 
 8# following ordered arguments:
 9#
10#   [1] REPOS-PATH   (the path to this repository)
11#   [2] USER         (the user who destroyed the lock)
12#
13# The paths that were just unlocked are passed to the hook via STDIN
14# (as of Subversion 1.2, only one path is passed per invocation, but
15# the plan is to pass all unlocked paths at once, so the hook program
16# should be written accordingly).
17#
18# The default working directory for the invocation is undefined, so
19# the program should set one explicitly if it cares.
20#
21# Because the lock has already been destroyed and cannot be undone,
22# the exit code of the hook program is ignored.
23#
24# On a Unix system, the normal procedure is to have 'post-unlock'
25# invoke other programs to do the real work, though it may do the
26# work itself too.
27#
28# Note that 'post-unlock' must be executable by the user(s) who will
29# invoke it (typically the user httpd runs as), and that user must
30# have filesystem-level permission to access the repository.
31#
32# On a Windows system, you should name the hook program
33# 'post-unlock.bat' or 'post-unlock.exe',
34# but the basic idea is the same.
35# 
36# Here is an example hook script, for a Unix /bin/sh interpreter:
37
38REPOS="$1"
39USER="$2"
40
41# Send email to interested parties, let them know a lock was removed:
42mailer.py unlock "$REPOS" "$USER" /path/to/mailer.conf