?

Log in

No account? Create an account

Commit Triggers sometimes needed for revision control...

« previous entry | next entry »
Oct. 21st, 2007 | 02:12 pm

When you "commit" a changeset in most source control systems you can
run a trigger.

Sometimes the trigger sends out email, sometimes it just checks for a
common mistake.

These are the ones I need for myself, and others:

  • Check all comments for spelling errors.
  • Check all comments against Google. If Google returns no
    results, the comment probably won't parse when a human reads it.
  • Flag all swear words. AKA #ifdef CRAP
  • Check blood alcohol content (not a problem I have...)
  • Check caffeine level (a problem I have...)
  • Did "make test" really get run before the code was pushed?
  • ...
  • Link | Leave a comment | Share

    Comments {3}

    (no subject)

    from: chexonte
    date: Oct. 22nd, 2007 09:29 am (UTC)
    Link

    ha!
    need to setup caffeine level check sfor myself :-)

    Reply | Thread

    Sue

    (no subject)

    from: siouxiequeue
    date: Oct. 22nd, 2007 01:01 pm (UTC)
    Link

    so.... are you checking whether the caffiene level is high enough, or low enough...? Just curious....

    Reply | Thread

    Brian "Krow" Aker

    (no subject)

    from: krow
    date: Oct. 22nd, 2007 05:54 pm (UTC)
    Link

    When I crash I can do just about nothing :(

    Reply | Parent | Thread