Source Version Control Repositories Customization and Hooks

This document briefly describes how you can use the tools at https://my.cae.wisc.edu/ to customize a repository you own.

Customization

In order to provide a scalable and maintainable service, we do not currently allow for custom repository hooks or additional changes outside of those available in the web pages.
Below are a set of other customization settings we do currently offer.
Please email unix-request@cae.wisc.edu if you have any questions or suggestions.

  • Hidden (on by default)
    Some of the repository browsing pages have the ability to list the available set of projects. This setting removes the project from that listing. Authentication and Authorization rules still apply to accessing them.
  • Commit Notifications
    An optional space separated list of email addresses that should receive commit/push notification emails. If left unset, then no commit notifications will be sent.

    These emails are sent out as the_commiter@cae.wisc.edu, but bounce messages will go back to the_owner@cae.wisc.edu.
    The messages can also be truncated to a particular owner defined length to prevent flooding peoples emails with excessively large diffs. The default message size is currently capped at 1M.

    For git repositories, the emails consist of a summary of the log messages of each of the commits involved in a push followed by an overall diff summary of the changes.

  • Commit Notification Branches
    NOTE: This hook customization is only available for git repositories.
    An optional space separated list of branches that should trigger commit notifications when pushed to the server. This settings has no effect if the commit notifications email list is not also set.
  • Production Branch
    NOTE: This hook customization is only available for git repositories.
    An optional name of a branch to consider as "production".
  • Production Group
    NOTE: This hook customization is only available for git repositories.
    An extra group whose membership is required to be able to push to the Production Branch.
  • Testing Branch
    NOTE: This hook customization is only available for git repositories.
    An optional name of a branch to consider as "testing". If set, then commits must be pushed here prior to being pushed to the Production Branch.
  • Require Merge Commit Branches
    NOTE: This hook customization is only available for git repositories.
    An optional space separated list of branch names to require merge commits on (ie: git merge --no-ff --log). Often set to the set of "Production Branch" and "Testing Branch" values.
  • Deny Non-FastForward Pushes
    NOTE: This hook customization is only available for git repositories.
    Whether or not to allow forced non-fastforward pushes (ie: pushing rebased branches). This controls the server side receive.denyNonFastForwards setting.

See Also:




Keywords:trac customization customize custom hook hooks my repo repository git svn subversion hg mercurial   Doc ID:22526
Owner:Brian K.Group:Computer-Aided Engineering
Created:2012-02-02 16:07 CDTUpdated:2016-07-05 14:12 CDT
Sites:Computer-Aided Engineering
Feedback:  0   0