Channels ▼

Using Server-Side Hooks On Subversion and Git

Assembla has released a library of server-side hooks for enhanced workflow and collaboration. Intended to bring control over repositories and source code management, this server-side hook library gives extra power to developers and system administrators.

More Insights

White Papers

More >>


More >>


More >>

Amid unconfirmed claims of being "first to market" for a "never before available" offering, Assembla CTO Michael Chletsos says that until now, server-side hooks have only been available for those who maintain their own repositories. He further claims that this requires hardware, infrastructure, and administration.

NOTE: Server-side hooks are scripts that run both before and after content is pushed to the server.

If the "min length" server-side hook is installed, a user can set a minimum required length for the commit message. If code is committed without a commit message of a certain minimum length, the code is rejected and not committed.

This ensures commit messages are properly formatted. The benefits of server-side hooks extend to any tasks requiring automation that relies on external web hooks, including checking code for syntax. In short, it makes it easy to manage multiple contributions from a distributed team to a single repository and prevents commits that do not comply with coding standards.

"In addition to providing a library of server-side hooks, Assembla allows users to contribute their own hooks. If a hook is approved, we will make them available for everyone to use," said Chletsos.

Server-side hooks are currently available in Assembla's Subversion and Git code repositories.

Related Reading

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.