doc/how-it-works
changeset 112 3035990989ee
parent 100 db219a5a14f8
equal deleted inserted replaced
111:eace50ec6427 112:3035990989ee
    16 the identifier for the developer. These keys will live in the "keys"
    16 the identifier for the developer. These keys will live in the "keys"
    17 subdirectory "/etc/mercurial-server" and the "keys" subdirectory of a
    17 subdirectory "/etc/mercurial-server" and the "keys" subdirectory of a
    18 repository called "hgadmin". A hook in this repository re-runs
    18 repository called "hgadmin". A hook in this repository re-runs
    19 "refresh-auth" on the most recent version after every push.
    19 "refresh-auth" on the most recent version after every push.
    20 
    20 
    21 Finally, hook in an extension is run for each changeset that is remotely
    21 When users try to commit new changesets, a hook is run which consults the
    22 committed, which uses the rules file to determine whether to allow the
    22 rules file to decide whether to allow the changeset into the repository.
    23 changeset.
    23 This can depend not only on the user and the repository, but also the
       
    24 branch and files in the changeset.