comparison en/branch.tex @ 207:54ca4e00e569

Add an example hook to enforce branch naming.

206:6519f3b983b4

In the simplest case, giving a name to each branch gives you a
permanent record of which branch a changeset originated on.  This
gives you a more context when you're trying to follow the history of a
long-lived branchy project.

If you're working with multiple shared repositories, you can set up a
hook on each that will block incoming changes that have the ``wrong''
branch name.  This provides a simple, but effective, defence against
people accidentally pushing changes from a ``bleeding edge'' branch to
a ``stable'' branch.

%%% Local Variables: 
%%% mode: latex
%%% TeX-master: "00book"
%%% End: 

207:54ca4e00e569

In the simplest case, giving a name to each branch gives you a
permanent record of which branch a changeset originated on.  This
gives you a more context when you're trying to follow the history of a
long-lived branchy project.

If you're working with shared repositories, you can set up a
\hook{pretxnchangegroup} hook on each that will block incoming changes
that have the ``wrong'' branch name.  This provides a simple, but
effective, defence against people accidentally pushing changes from a
``bleeding edge'' branch to a ``stable'' branch.  Such a hook might
look like this inside the shared repo's \hgrc.
\begin{codesample2}
  [hooks]
  pretxnchangegroup.branch = hg heads --template '{branches} ' | grep mybranch
\end{codesample2}

%%% Local Variables: 
%%% mode: latex
%%% TeX-master: "00book"
%%% End: