The Hackerlab at `regexps.com`

## Using Triggers

up: arch next: Automatic Triggers prev: arch Triggers

This chapter describes two ways to use triggers: for sending email about changes to an archive, and for keeping a revision library up to date (see Revision Tree Libraries).

### Sending Email Notices About Repository Changes

`arch` provides four commands designed for use as triggers that send email about changes to a repository. (See arch Triggers.) These are:

            larch mail-new-categories
            larch mail-new-branches
            larch mail-new-versions
            larch mail-new-revisions

You can create a triggers for sending email with a `notify` `=rules.archives` configuration rule such as this (here split over multiple lines to fit the printed page -- in practice, this rule would be on one line):

            joe.hacker--2002@gnu.org
                    mail-new-categories:joe@gnu.org
                    mail-new-branches:joe@gnu.org
                    mail-new-versions:joe@gnu.org
                    mail-new-revisions:joe@gnu.org

### Updating a Revision Library

You can use triggers to keep a revision library automatically up-to-date with a rule like this:

            joe.hacker--2002@gnu.org
                    noop:
                    noop:
                    noop:
                    library-add:--ignore-extra-args

arch: The arch Revision Control System
The Hackerlab at `regexps.com`