commit
d76c83f948
|
@ -135,7 +135,7 @@ When `gl-auth-command` gets control, it looks at the first argument
|
||||||
`SSH_ORIGINAL_COMMAND` variable to find out which repository you want to
|
`SSH_ORIGINAL_COMMAND` variable to find out which repository you want to
|
||||||
access, and whether you're reading or writing.
|
access, and whether you're reading or writing.
|
||||||
|
|
||||||
Now is has user, repository, and access requested (read/write), gitolite looks
|
Now that it has a user, repository, and access requested (read/write), gitolite looks
|
||||||
at its config file, and either allows or rejects the request.
|
at its config file, and either allows or rejects the request.
|
||||||
|
|
||||||
But this cannot differentiate between different branches within a repo; that
|
But this cannot differentiate between different branches within a repo; that
|
||||||
|
@ -155,7 +155,7 @@ happen -- see `git help hooks` for details. One of those hooks is the
|
||||||
tag is about to be updated. The hook is passed the name of the branch or tag,
|
tag is about to be updated. The hook is passed the name of the branch or tag,
|
||||||
the old SHA1 value, and the new SHA1 value, as arguments. Hooks that are
|
the old SHA1 value, and the new SHA1 value, as arguments. Hooks that are
|
||||||
called *before* an action happens are allowed to prevent that action from
|
called *before* an action happens are allowed to prevent that action from
|
||||||
happening y returning an error code.
|
happening by returning an error code.
|
||||||
|
|
||||||
When gitolite is told to create a new repository (by the admin), it installs
|
When gitolite is told to create a new repository (by the admin), it installs
|
||||||
a special update hook. This hook takes all the information presented, looks
|
a special update hook. This hook takes all the information presented, looks
|
||||||
|
|
Loading…
Reference in a new issue