Subversion Hooks

Rice Subversion Repository Hooks

We currently support the following hooks for any repository.
Use the links below to find out how to activate any of these hooks for your repository and to find out what these hooks do.

• Pre-Commit Hooks
  • check-case-insensitive
  • check-mime-type
  • detect-merge-conflicts
• Post-Commit Hooks
  • commit-email

What is a Subversion Repository Hook?

A hook is a program triggered by some repository event, such as the creation of a new revision or the modification of an unversioned property. Some hooks (the so-called "pre hooks") run in advance of a repository operation and provide a means by which to both report what is about to happen and to prevent it from happening at all. Other hooks (the "post hooks") run after the completion of a repository event, and are useful for performing tasks that examine—but don't modify—the repository. Each hook is handed enough information to tell what that event is (or was), the specific repository changes proposed (or completed), and the username of the person who triggered the event.

What is a Pre-Commit Hook?

The pre-commit hook is run just before a commit transaction is promoted to a new revision. Typically, this hook is used to protect against commits that are disallowed due to content or location (for example, your site might require that all commits to a certain branch include a ticket number from the bug tracker, or that the incoming log message is non-empty).

What is a Post-Commit Hook?

The post-commit hook is run after the transaction is committed, and a new revision created. Most people use this hook to send out descriptive emails about the commit or to notify some other tool (such as an issue tracker) that a commit has happened. Some configurations also use this hook to trigger backup processes.

Subversion Maintenance Schedule

Regular maintenance

• Monday mornings from 8am to 9am

Next Repository group creation

• July 27th 8am - 8pm.