authlogic-oauth 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (60) hide show
  1. data/.git/COMMIT_EDITMSG +71 -0
  2. data/.git/FETCH_HEAD +1 -0
  3. data/.git/HEAD +1 -0
  4. data/.git/config +12 -0
  5. data/.git/description +1 -0
  6. data/.git/hooks/applypatch-msg.sample +15 -0
  7. data/.git/hooks/commit-msg.sample +24 -0
  8. data/.git/hooks/post-commit.sample +8 -0
  9. data/.git/hooks/post-receive.sample +15 -0
  10. data/.git/hooks/post-update.sample +8 -0
  11. data/.git/hooks/pre-applypatch.sample +14 -0
  12. data/.git/hooks/pre-commit.sample +18 -0
  13. data/.git/hooks/pre-rebase.sample +169 -0
  14. data/.git/hooks/prepare-commit-msg.sample +36 -0
  15. data/.git/hooks/update.sample +107 -0
  16. data/.git/index +0 -0
  17. data/.git/info/exclude +6 -0
  18. data/.git/logs/HEAD +8 -0
  19. data/.git/logs/refs/heads/master +6 -0
  20. data/.git/logs/refs/remotes/origin/HEAD +1 -0
  21. data/.git/logs/refs/remotes/origin/master +5 -0
  22. data/.git/objects/1a/7e60fbbc011b519f1f19dbca839cfd907924a3 +0 -0
  23. data/.git/objects/2e/f242d63b205e88b003d10e96d7d31269bd7073 +0 -0
  24. data/.git/objects/41/6b196f0d3fa02be32bdd0bd7d6a3fd7d57844d +0 -0
  25. data/.git/objects/42/607cc77682553f3d71ef40e5fae408ac3351f4 +0 -0
  26. data/.git/objects/56/6625e05678ab5d52511225fa360e6934e049f6 +0 -0
  27. data/.git/objects/56/947322f2e948b597b9e692320ecada30315e45 +0 -0
  28. data/.git/objects/87/a7f6af123ffd70a8cd751b80ec4d4a9de69ab9 +0 -0
  29. data/.git/objects/ab/14db4dd48cb6f4c3688eb65513afac383d3584 +0 -0
  30. data/.git/objects/b2/9bfce970d5a817d2f7626b2984dc8de67ab774 +0 -0
  31. data/.git/objects/e0/a81debca6c11c68732b3769d1f83c5c3c97c09 +0 -0
  32. data/.git/objects/e3/74f7848330d167432299a84e43c7af18a51b87 +2 -0
  33. data/.git/objects/f3/5e9e44d75a11221b0c2f2b2a0bdb5b37bfbaa1 +0 -0
  34. data/.git/objects/pack/pack-2b55f15bfde87d738b79905b5c0788e4a4cbf3af.idx +0 -0
  35. data/.git/objects/pack/pack-2b55f15bfde87d738b79905b5c0788e4a4cbf3af.pack +0 -0
  36. data/.git/packed-refs +2 -0
  37. data/.git/refs/heads/master +1 -0
  38. data/.git/refs/remotes/origin/HEAD +1 -0
  39. data/.git/refs/remotes/origin/master +1 -0
  40. data/CHANGELOG.rdoc +4 -0
  41. data/MIT-LICENSE +20 -0
  42. data/Manifest.txt +57 -0
  43. data/README.rdoc +120 -0
  44. data/Rakefile +20 -0
  45. data/init.rb +1 -0
  46. data/lib/authlogic_oauth/acts_as_authentic.rb +116 -0
  47. data/lib/authlogic_oauth/oauth_process.rb +61 -0
  48. data/lib/authlogic_oauth/session.rb +73 -0
  49. data/lib/authlogic_oauth/version.rb +51 -0
  50. data/lib/authlogic_oauth.rb +7 -0
  51. data/rails/init.rb +1 -0
  52. data/test/acts_as_authentic_test.rb +100 -0
  53. data/test/fixtures/users.yml +6 -0
  54. data/test/lib/user.rb +3 -0
  55. data/test/lib/user_session.rb +7 -0
  56. data/test/session_test.rb +27 -0
  57. data/test/test_helper.rb +49 -0
  58. data.tar.gz.sig +0 -0
  59. metadata +155 -0
  60. metadata.gz.sig +0 -0
@@ -0,0 +1,71 @@
1
+ Updating Manifest
2
+ # Please enter the commit message for your changes. Lines starting
3
+ # with '#' will be ignored, and an empty message aborts the commit.
4
+ # On branch master
5
+ # Changes to be committed:
6
+ # (use "git reset HEAD <file>..." to unstage)
7
+ #
8
+ # modified: Manifest.txt
9
+ #
10
+ diff --git a/Manifest.txt b/Manifest.txt
11
+ index e69de29..844923a 100644
12
+ --- a/Manifest.txt
13
+ +++ b/Manifest.txt
14
+ @@ -0,0 +1,57 @@
15
+ +.git/COMMIT_EDITMSG
16
+ +.git/FETCH_HEAD
17
+ +.git/HEAD
18
+ +.git/config
19
+ +.git/description
20
+ +.git/hooks/applypatch-msg.sample
21
+ +.git/hooks/commit-msg.sample
22
+ +.git/hooks/post-commit.sample
23
+ +.git/hooks/post-receive.sample
24
+ +.git/hooks/post-update.sample
25
+ +.git/hooks/pre-applypatch.sample
26
+ +.git/hooks/pre-commit.sample
27
+ +.git/hooks/pre-rebase.sample
28
+ +.git/hooks/prepare-commit-msg.sample
29
+ +.git/hooks/update.sample
30
+ +.git/index
31
+ +.git/info/exclude
32
+ +.git/logs/HEAD
33
+ +.git/logs/refs/heads/master
34
+ +.git/logs/refs/remotes/origin/HEAD
35
+ +.git/logs/refs/remotes/origin/master
36
+ +.git/objects/1a/7e60fbbc011b519f1f19dbca839cfd907924a3
37
+ +.git/objects/2e/f242d63b205e88b003d10e96d7d31269bd7073
38
+ +.git/objects/41/6b196f0d3fa02be32bdd0bd7d6a3fd7d57844d
39
+ +.git/objects/42/607cc77682553f3d71ef40e5fae408ac3351f4
40
+ +.git/objects/56/6625e05678ab5d52511225fa360e6934e049f6
41
+ +.git/objects/56/947322f2e948b597b9e692320ecada30315e45
42
+ +.git/objects/87/a7f6af123ffd70a8cd751b80ec4d4a9de69ab9
43
+ +.git/objects/ab/14db4dd48cb6f4c3688eb65513afac383d3584
44
+ +.git/objects/b2/9bfce970d5a817d2f7626b2984dc8de67ab774
45
+ +.git/objects/e0/a81debca6c11c68732b3769d1f83c5c3c97c09
46
+ +.git/objects/e3/74f7848330d167432299a84e43c7af18a51b87
47
+ +.git/objects/f3/5e9e44d75a11221b0c2f2b2a0bdb5b37bfbaa1
48
+ +.git/objects/pack/pack-2b55f15bfde87d738b79905b5c0788e4a4cbf3af.idx
49
+ +.git/objects/pack/pack-2b55f15bfde87d738b79905b5c0788e4a4cbf3af.pack
50
+ +.git/packed-refs
51
+ +.git/refs/heads/master
52
+ +.git/refs/remotes/origin/HEAD
53
+ +.git/refs/remotes/origin/master
54
+ +CHANGELOG.rdoc
55
+ +MIT-LICENSE
56
+ +Manifest.txt
57
+ +README.rdoc
58
+ +Rakefile
59
+ +init.rb
60
+ +lib/authlogic_oauth.rb
61
+ +lib/authlogic_oauth/acts_as_authentic.rb
62
+ +lib/authlogic_oauth/oauth_process.rb
63
+ +lib/authlogic_oauth/session.rb
64
+ +lib/authlogic_oauth/version.rb
65
+ +rails/init.rb
66
+ +test/acts_as_authentic_test.rb
67
+ +test/fixtures/users.yml
68
+ +test/lib/user.rb
69
+ +test/lib/user_session.rb
70
+ +test/session_test.rb
71
+ +test/test_helper.rb
data/.git/FETCH_HEAD ADDED
@@ -0,0 +1 @@
1
+ 42607cc77682553f3d71ef40e5fae408ac3351f4 branch 'master' of git@github.com:jrallison/authlogic_oauth
data/.git/HEAD ADDED
@@ -0,0 +1 @@
1
+ ref: refs/heads/master
data/.git/config ADDED
@@ -0,0 +1,12 @@
1
+ [core]
2
+ repositoryformatversion = 0
3
+ filemode = true
4
+ bare = false
5
+ logallrefupdates = true
6
+ ignorecase = true
7
+ [remote "origin"]
8
+ url = git@github.com:jrallison/authlogic_oauth.git
9
+ fetch = +refs/heads/*:refs/remotes/origin/*
10
+ [branch "master"]
11
+ remote = origin
12
+ merge = refs/heads/master
data/.git/description ADDED
@@ -0,0 +1 @@
1
+ Unnamed repository; edit this file to name it for gitweb.
@@ -0,0 +1,15 @@
1
+ #!/bin/sh
2
+ #
3
+ # An example hook script to check the commit log message taken by
4
+ # applypatch from an e-mail message.
5
+ #
6
+ # The hook should exit with non-zero status after issuing an
7
+ # appropriate message if it wants to stop the commit. The hook is
8
+ # allowed to edit the commit message file.
9
+ #
10
+ # To enable this hook, rename this file to "applypatch-msg".
11
+
12
+ . git-sh-setup
13
+ test -x "$GIT_DIR/hooks/commit-msg" &&
14
+ exec "$GIT_DIR/hooks/commit-msg" ${1+"$@"}
15
+ :
@@ -0,0 +1,24 @@
1
+ #!/bin/sh
2
+ #
3
+ # An example hook script to check the commit log message.
4
+ # Called by git-commit with one argument, the name of the file
5
+ # that has the commit message. The hook should exit with non-zero
6
+ # status after issuing an appropriate message if it wants to stop the
7
+ # commit. The hook is allowed to edit the commit message file.
8
+ #
9
+ # To enable this hook, rename this file to "commit-msg".
10
+
11
+ # Uncomment the below to add a Signed-off-by line to the message.
12
+ # Doing this in a hook is a bad idea in general, but the prepare-commit-msg
13
+ # hook is more suited to it.
14
+ #
15
+ # SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
16
+ # grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
17
+
18
+ # This example catches duplicate Signed-off-by lines.
19
+
20
+ test "" = "$(grep '^Signed-off-by: ' "$1" |
21
+ sort | uniq -c | sed -e '/^[ ]*1[ ]/d')" || {
22
+ echo >&2 Duplicate Signed-off-by lines.
23
+ exit 1
24
+ }
@@ -0,0 +1,8 @@
1
+ #!/bin/sh
2
+ #
3
+ # An example hook script that is called after a successful
4
+ # commit is made.
5
+ #
6
+ # To enable this hook, rename this file to "post-commit".
7
+
8
+ : Nothing
@@ -0,0 +1,15 @@
1
+ #!/bin/sh
2
+ #
3
+ # An example hook script for the "post-receive" event.
4
+ #
5
+ # The "post-receive" script is run after receive-pack has accepted a pack
6
+ # and the repository has been updated. It is passed arguments in through
7
+ # stdin in the form
8
+ # <oldrev> <newrev> <refname>
9
+ # For example:
10
+ # aa453216d1b3e49e7f6f98441fa56946ddcd6a20 68f7abf4e6f922807889f52bc043ecd31b79f814 refs/heads/master
11
+ #
12
+ # see contrib/hooks/ for an sample, or uncomment the next line and
13
+ # rename the file to "post-receive".
14
+
15
+ #. /usr/share/doc/git-core/contrib/hooks/post-receive-email
@@ -0,0 +1,8 @@
1
+ #!/bin/sh
2
+ #
3
+ # An example hook script to prepare a packed repository for use over
4
+ # dumb transports.
5
+ #
6
+ # To enable this hook, rename this file to "post-update".
7
+
8
+ exec git-update-server-info
@@ -0,0 +1,14 @@
1
+ #!/bin/sh
2
+ #
3
+ # An example hook script to verify what is about to be committed
4
+ # by applypatch from an e-mail message.
5
+ #
6
+ # The hook should exit with non-zero status after issuing an
7
+ # appropriate message if it wants to stop the commit.
8
+ #
9
+ # To enable this hook, rename this file to "pre-applypatch".
10
+
11
+ . git-sh-setup
12
+ test -x "$GIT_DIR/hooks/pre-commit" &&
13
+ exec "$GIT_DIR/hooks/pre-commit" ${1+"$@"}
14
+ :
@@ -0,0 +1,18 @@
1
+ #!/bin/sh
2
+ #
3
+ # An example hook script to verify what is about to be committed.
4
+ # Called by git-commit with no arguments. The hook should
5
+ # exit with non-zero status after issuing an appropriate message if
6
+ # it wants to stop the commit.
7
+ #
8
+ # To enable this hook, rename this file to "pre-commit".
9
+
10
+ if git-rev-parse --verify HEAD 2>/dev/null
11
+ then
12
+ against=HEAD
13
+ else
14
+ # Initial commit: diff against an empty tree object
15
+ against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
16
+ fi
17
+
18
+ exec git diff-index --check --cached $against --
@@ -0,0 +1,169 @@
1
+ #!/bin/sh
2
+ #
3
+ # Copyright (c) 2006, 2008 Junio C Hamano
4
+ #
5
+ # The "pre-rebase" hook is run just before "git-rebase" starts doing
6
+ # its job, and can prevent the command from running by exiting with
7
+ # non-zero status.
8
+ #
9
+ # The hook is called with the following parameters:
10
+ #
11
+ # $1 -- the upstream the series was forked from.
12
+ # $2 -- the branch being rebased (or empty when rebasing the current branch).
13
+ #
14
+ # This sample shows how to prevent topic branches that are already
15
+ # merged to 'next' branch from getting rebased, because allowing it
16
+ # would result in rebasing already published history.
17
+
18
+ publish=next
19
+ basebranch="$1"
20
+ if test "$#" = 2
21
+ then
22
+ topic="refs/heads/$2"
23
+ else
24
+ topic=`git symbolic-ref HEAD` ||
25
+ exit 0 ;# we do not interrupt rebasing detached HEAD
26
+ fi
27
+
28
+ case "$topic" in
29
+ refs/heads/??/*)
30
+ ;;
31
+ *)
32
+ exit 0 ;# we do not interrupt others.
33
+ ;;
34
+ esac
35
+
36
+ # Now we are dealing with a topic branch being rebased
37
+ # on top of master. Is it OK to rebase it?
38
+
39
+ # Does the topic really exist?
40
+ git show-ref -q "$topic" || {
41
+ echo >&2 "No such branch $topic"
42
+ exit 1
43
+ }
44
+
45
+ # Is topic fully merged to master?
46
+ not_in_master=`git-rev-list --pretty=oneline ^master "$topic"`
47
+ if test -z "$not_in_master"
48
+ then
49
+ echo >&2 "$topic is fully merged to master; better remove it."
50
+ exit 1 ;# we could allow it, but there is no point.
51
+ fi
52
+
53
+ # Is topic ever merged to next? If so you should not be rebasing it.
54
+ only_next_1=`git-rev-list ^master "^$topic" ${publish} | sort`
55
+ only_next_2=`git-rev-list ^master ${publish} | sort`
56
+ if test "$only_next_1" = "$only_next_2"
57
+ then
58
+ not_in_topic=`git-rev-list "^$topic" master`
59
+ if test -z "$not_in_topic"
60
+ then
61
+ echo >&2 "$topic is already up-to-date with master"
62
+ exit 1 ;# we could allow it, but there is no point.
63
+ else
64
+ exit 0
65
+ fi
66
+ else
67
+ not_in_next=`git-rev-list --pretty=oneline ^${publish} "$topic"`
68
+ perl -e '
69
+ my $topic = $ARGV[0];
70
+ my $msg = "* $topic has commits already merged to public branch:\n";
71
+ my (%not_in_next) = map {
72
+ /^([0-9a-f]+) /;
73
+ ($1 => 1);
74
+ } split(/\n/, $ARGV[1]);
75
+ for my $elem (map {
76
+ /^([0-9a-f]+) (.*)$/;
77
+ [$1 => $2];
78
+ } split(/\n/, $ARGV[2])) {
79
+ if (!exists $not_in_next{$elem->[0]}) {
80
+ if ($msg) {
81
+ print STDERR $msg;
82
+ undef $msg;
83
+ }
84
+ print STDERR " $elem->[1]\n";
85
+ }
86
+ }
87
+ ' "$topic" "$not_in_next" "$not_in_master"
88
+ exit 1
89
+ fi
90
+
91
+ exit 0
92
+
93
+ ################################################################
94
+
95
+ This sample hook safeguards topic branches that have been
96
+ published from being rewound.
97
+
98
+ The workflow assumed here is:
99
+
100
+ * Once a topic branch forks from "master", "master" is never
101
+ merged into it again (either directly or indirectly).
102
+
103
+ * Once a topic branch is fully cooked and merged into "master",
104
+ it is deleted. If you need to build on top of it to correct
105
+ earlier mistakes, a new topic branch is created by forking at
106
+ the tip of the "master". This is not strictly necessary, but
107
+ it makes it easier to keep your history simple.
108
+
109
+ * Whenever you need to test or publish your changes to topic
110
+ branches, merge them into "next" branch.
111
+
112
+ The script, being an example, hardcodes the publish branch name
113
+ to be "next", but it is trivial to make it configurable via
114
+ $GIT_DIR/config mechanism.
115
+
116
+ With this workflow, you would want to know:
117
+
118
+ (1) ... if a topic branch has ever been merged to "next". Young
119
+ topic branches can have stupid mistakes you would rather
120
+ clean up before publishing, and things that have not been
121
+ merged into other branches can be easily rebased without
122
+ affecting other people. But once it is published, you would
123
+ not want to rewind it.
124
+
125
+ (2) ... if a topic branch has been fully merged to "master".
126
+ Then you can delete it. More importantly, you should not
127
+ build on top of it -- other people may already want to
128
+ change things related to the topic as patches against your
129
+ "master", so if you need further changes, it is better to
130
+ fork the topic (perhaps with the same name) afresh from the
131
+ tip of "master".
132
+
133
+ Let's look at this example:
134
+
135
+ o---o---o---o---o---o---o---o---o---o "next"
136
+ / / / /
137
+ / a---a---b A / /
138
+ / / / /
139
+ / / c---c---c---c B /
140
+ / / / \ /
141
+ / / / b---b C \ /
142
+ / / / / \ /
143
+ ---o---o---o---o---o---o---o---o---o---o---o "master"
144
+
145
+
146
+ A, B and C are topic branches.
147
+
148
+ * A has one fix since it was merged up to "next".
149
+
150
+ * B has finished. It has been fully merged up to "master" and "next",
151
+ and is ready to be deleted.
152
+
153
+ * C has not merged to "next" at all.
154
+
155
+ We would want to allow C to be rebased, refuse A, and encourage
156
+ B to be deleted.
157
+
158
+ To compute (1):
159
+
160
+ git-rev-list ^master ^topic next
161
+ git-rev-list ^master next
162
+
163
+ if these match, topic has not merged in next at all.
164
+
165
+ To compute (2):
166
+
167
+ git-rev-list master..topic
168
+
169
+ if this is empty, it is fully merged to "master".
@@ -0,0 +1,36 @@
1
+ #!/bin/sh
2
+ #
3
+ # An example hook script to prepare the commit log message.
4
+ # Called by git-commit with the name of the file that has the
5
+ # commit message, followed by the description of the commit
6
+ # message's source. The hook's purpose is to edit the commit
7
+ # message file. If the hook fails with a non-zero status,
8
+ # the commit is aborted.
9
+ #
10
+ # To enable this hook, rename this file to "prepare-commit-msg".
11
+
12
+ # This hook includes three examples. The first comments out the
13
+ # "Conflicts:" part of a merge commit.
14
+ #
15
+ # The second includes the output of "git diff --name-status -r"
16
+ # into the message, just before the "git status" output. It is
17
+ # commented because it doesn't cope with --amend or with squashed
18
+ # commits.
19
+ #
20
+ # The third example adds a Signed-off-by line to the message, that can
21
+ # still be edited. This is rarely a good idea.
22
+
23
+ case "$2,$3" in
24
+ merge,)
25
+ perl -i.bak -ne 's/^/# /, s/^# #/#/ if /^Conflicts/ .. /#/; print' "$1" ;;
26
+
27
+ # ,|template,)
28
+ # perl -i.bak -pe '
29
+ # print "\n" . `git diff --cached --name-status -r`
30
+ # if /^#/ && $first++ == 0' "$1" ;;
31
+
32
+ *) ;;
33
+ esac
34
+
35
+ # SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
36
+ # grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
@@ -0,0 +1,107 @@
1
+ #!/bin/sh
2
+ #
3
+ # An example hook script to blocks unannotated tags from entering.
4
+ # Called by git-receive-pack with arguments: refname sha1-old sha1-new
5
+ #
6
+ # To enable this hook, rename this file to "update".
7
+ #
8
+ # Config
9
+ # ------
10
+ # hooks.allowunannotated
11
+ # This boolean sets whether unannotated tags will be allowed into the
12
+ # repository. By default they won't be.
13
+ # hooks.allowdeletetag
14
+ # This boolean sets whether deleting tags will be allowed in the
15
+ # repository. By default they won't be.
16
+ # hooks.allowdeletebranch
17
+ # This boolean sets whether deleting branches will be allowed in the
18
+ # repository. By default they won't be.
19
+ #
20
+
21
+ # --- Command line
22
+ refname="$1"
23
+ oldrev="$2"
24
+ newrev="$3"
25
+
26
+ # --- Safety check
27
+ if [ -z "$GIT_DIR" ]; then
28
+ echo "Don't run this script from the command line." >&2
29
+ echo " (if you want, you could supply GIT_DIR then run" >&2
30
+ echo " $0 <ref> <oldrev> <newrev>)" >&2
31
+ exit 1
32
+ fi
33
+
34
+ if [ -z "$refname" -o -z "$oldrev" -o -z "$newrev" ]; then
35
+ echo "Usage: $0 <ref> <oldrev> <newrev>" >&2
36
+ exit 1
37
+ fi
38
+
39
+ # --- Config
40
+ allowunannotated=$(git config --bool hooks.allowunannotated)
41
+ allowdeletebranch=$(git config --bool hooks.allowdeletebranch)
42
+ allowdeletetag=$(git config --bool hooks.allowdeletetag)
43
+
44
+ # check for no description
45
+ projectdesc=$(sed -e '1q' "$GIT_DIR/description")
46
+ if [ -z "$projectdesc" -o "$projectdesc" = "Unnamed repository; edit this file to name it for gitweb." ]; then
47
+ echo "*** Project description file hasn't been set" >&2
48
+ exit 1
49
+ fi
50
+
51
+ # --- Check types
52
+ # if $newrev is 0000...0000, it's a commit to delete a ref.
53
+ if [ "$newrev" = "0000000000000000000000000000000000000000" ]; then
54
+ newrev_type=delete
55
+ else
56
+ newrev_type=$(git-cat-file -t $newrev)
57
+ fi
58
+
59
+ case "$refname","$newrev_type" in
60
+ refs/tags/*,commit)
61
+ # un-annotated tag
62
+ short_refname=${refname##refs/tags/}
63
+ if [ "$allowunannotated" != "true" ]; then
64
+ echo "*** The un-annotated tag, $short_refname, is not allowed in this repository" >&2
65
+ echo "*** Use 'git tag [ -a | -s ]' for tags you want to propagate." >&2
66
+ exit 1
67
+ fi
68
+ ;;
69
+ refs/tags/*,delete)
70
+ # delete tag
71
+ if [ "$allowdeletetag" != "true" ]; then
72
+ echo "*** Deleting a tag is not allowed in this repository" >&2
73
+ exit 1
74
+ fi
75
+ ;;
76
+ refs/tags/*,tag)
77
+ # annotated tag
78
+ ;;
79
+ refs/heads/*,commit)
80
+ # branch
81
+ ;;
82
+ refs/heads/*,delete)
83
+ # delete branch
84
+ if [ "$allowdeletebranch" != "true" ]; then
85
+ echo "*** Deleting a branch is not allowed in this repository" >&2
86
+ exit 1
87
+ fi
88
+ ;;
89
+ refs/remotes/*,commit)
90
+ # tracking branch
91
+ ;;
92
+ refs/remotes/*,delete)
93
+ # delete tracking branch
94
+ if [ "$allowdeletebranch" != "true" ]; then
95
+ echo "*** Deleting a tracking branch is not allowed in this repository" >&2
96
+ exit 1
97
+ fi
98
+ ;;
99
+ *)
100
+ # Anything else (is there anything else?)
101
+ echo "*** Update hook: unknown type of update to ref $refname of type $newrev_type" >&2
102
+ exit 1
103
+ ;;
104
+ esac
105
+
106
+ # --- Finished
107
+ exit 0