https://github.com/davidparsson/pre-commit-scripts

A collection of pre-commit hook scripts for SVN.
https://github.com/davidparsson/pre-commit-scripts

Last synced: 16 days ago
JSON representation

A collection of pre-commit hook scripts for SVN.

• Host: GitHub
• URL: https://github.com/davidparsson/pre-commit-scripts
• Owner: davidparsson
• Created: 2012-05-07T11:04:48.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2012-08-24T07:01:06.000Z (about 12 years ago)
• Last Synced: 2023-04-09T23:58:07.319Z (over 1 year ago)
• Language: Python
• Homepage:
• Size: 188 KB
• Stars: 1
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
Pre-Commit Hooks

================

Contains the following pre-commit hooks:

- Require commit messages of a certain length

- Disallow modification of tagged files

- Require new files in certain folders to be added last, alphabetically

More details below.

### Usage

For an example of how to run the scripts in a hook, see the file `pre-commit-example`.


Usage: [script].py REPOS TXN


Run pre-commit verification on a repository transaction.

Options:

  -h, --help      show this help message and exit

  -r, --revision  Test mode. Specify a revision instead of a transaction.



Require Commit Message

----------------------

Requires all commit message to have a configured minimum length. Default is 3 characters.

Tagged Files Modification

-------------------------

Disallows any other changes than copy and delete on created and existing tagged files.

This check can be skipped by supplying a keyword in the commit message. Default is `skip-tag-check`.

Ordered Filename Commit

-----------------------

A pre-commit script in python checking that certain files are added, modified or removed

last in aplhabetical order.

This is for example useful in projects where database migration scripts are

executed alphabetically.

This check can be skipped by supplying a keyword in the commit message. Default is `skip-migration-check`.

### What it does

Consider an SVN repository with the following contents:


module1/

  db/

    01.migration

    02.migration

    04.migration

module2/

  db/

    03.migration

    05.migration

    06.migration



Assuming that the script is set up to match the `*.migration` files in the path `db/`

for every module, it would **not** be possible to commit a file named

`module1/db/05.migration` since a file named `06.migration` exists in module2.

A correct filename would rather be `module1/db/07.migration`.

Neither would it be possible to modify or remove any migration but

`module2/db/06.migration`.