Permalink
Switch branches/tags
Nothing to show
Commits on Jun 16, 2017
  1. Merge pull request #62 from emmetog/patch-2

    James Dinsdale
    James Dinsdale committed Jun 16, 2017
    Use "git-hooks" instead of "git hooks" in docs
Commits on Jun 9, 2017
  1. Merge pull request #61 from emmetog/patch-1

    James Dinsdale
    James Dinsdale committed Jun 9, 2017
    Improve installation instructions
Commits on Mar 5, 2017
  1. Merge pull request #45 from thequux/support-newer-find

    James Dinsdale
    James Dinsdale committed Mar 5, 2017
    Support newer versions of `find` that no longer support the "-perm +111" option.
Commits on Mar 4, 2017
  1. Re-add support for BSD and OSX, which don't support `-perm /111`

    thequux committed Mar 4, 2017
    Signed-off-by: TQ Hirsch <thequux@thequux.com>
Commits on Mar 3, 2017
  1. Merge pull request #39 from Zearin/patch-1

    James Dinsdale
    James Dinsdale committed Mar 3, 2017
    Minor rearrangement of README.md
  2. Merge pull request #43 from mparker17/contributing_guidelines

    James Dinsdale
    James Dinsdale committed Mar 3, 2017
    Add a CONTRIBUTING guide for potential contributors.
  3. Merge pull request #54 from Krettis/feature/better-visual-listing

    James Dinsdale
    James Dinsdale committed Mar 3, 2017
    A more clearer list
  4. Merge pull request #57 from hurrymaplelad/patch-1

    James Dinsdale
    James Dinsdale committed Mar 3, 2017
    Fix project hooks location
Commits on Nov 1, 2015
  1. Fix project hooks location

    hurrymaplelad committed Nov 1, 2015
    Fixes #56, why has this been open so long?
Commits on May 14, 2015
Commits on May 11, 2015
  1. Show the list more clearer

    Krettis committed May 11, 2015
    This is new:
    - No more use of tabs but equally spaces between hook and description
    - Mention what part of the git-hook it is instead of showing only
    directory (user, rep, etc)
    - Only mention once which subdirectory you are in (commit-msg,
    prepare…,etc)
    - Colors
  2. Don't show what has not build in.

    Krettis committed May 11, 2015
    Commented the supposed feature which does nothing.
Commits on Sep 8, 2014
  1. Support newer versions of `find` that no longer support the "-perm +111"

    thequux committed Sep 8, 2014
    option.
    
    Signed-off-by: TQ Hirsch <thequux@thequux.com>
Commits on Aug 15, 2014
  1. Add a CONTRIBUTING guide for potential contributors.

    mparker17 committed Aug 15, 2014
    To help bugs and feature requests move faster, it's handy to answer some
    of the basic questions a contributor might have. Github and
    pengwynn/flint (a linter that checks projects for common sources of
    contributor friction) recommend adding a CONTRIBUTING guide. Github will
    even show a little message at the top of the New Issue screen if your
    project has one.
    
    For more information, see
    https://help.github.com/articles/setting-guidelines-for-repository-contributors
    and
    https://github.com/pengwynn/flint
    
    As a bit of background, when I was writing my first pull request to this
    project, I almost didn't notice that the repository had it's own project
    hooks... I just happened to test my changes inside my development
    environment folder and saw they had appeared in the list.
    
    This adds a simple, informal CONTRIBUTING guide with sections on writing
    good issues, setting up a development environment (including a reminder
    to `git hooks --install`) and creating pull requests... mostly I
    reference Github's documentation.
    
    Signed-off-by: M Parker <mparker17@536298.no-reply.drupal.org>
Commits on Jun 15, 2014
  1. Minor rearrangement of README.md

    Tony
    Tony committed Jun 15, 2014
    Moved the instructions on listing hooks earlier in the document, and gave it a separate heading.
Commits on Apr 30, 2014
  1. Merge pull request #36 from Zearin/reorder-func

    icefox committed Apr 30, 2014
    Did you happen to enable git-hooks in the git-hooks repo?  It should have prevented you from making commits that were not signed off on.
Commits on Apr 28, 2014
  1. Update `--help` output

    Zearin
    Zearin committed Apr 28, 2014
    * No longer using `--severalunseparatewords` (but still accepts them for backwards compatibility)
    * Use `<angled brackets>` for mandatory arguments (`[square brackets]` are for optional arguments)
  2. Use consistent function names

    Zearin
    Zearin committed Apr 28, 2014
  3. Use consistent braces for functions

    Zearin
    Zearin committed Apr 28, 2014
  4. Put related functions next to each other

    Zearin
    Zearin committed Apr 28, 2014
Commits on Feb 18, 2014
  1. Don't output error when checking files that have been removed and don…

    icefox committed Feb 18, 2014
    …'t exists.
    
    Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
  2. Handle repository paths that contains spaces

    icefox committed Feb 18, 2014
    Issue #33
    
    Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Commits on Dec 5, 2013
  1. Merge pull request #29 from Zearin/patch-1

    icefox committed Dec 5, 2013
    Updated README to use markdown & edited for grammar, phrasing, and clarity
Commits on Dec 2, 2013
Commits on Nov 7, 2013
  1. Remove .gitignore which was just ignoring vim swap files

    icefox committed Nov 7, 2013
    which really belong in users global .gitignore file.
    
    Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
  2. Add the ability to remind users when committing to any repo without g…

    icefox committed Nov 7, 2013
    …it-hooks.
    
    It is easy to forget to install git-hooks in a repository you are using.
    A commit with no error message could both mean you don't have git-hooks
    installed and it can mean that you do have it installed, but your
    commit was perfect and there was no errors.
    
    The new option --installglobal creates a default .git template
    that is used by all future cloned repositories (and git init'd)
    that remind users that the repository doesn't have git-hooks
    installed.
    
    A number of projects I have been involved with used git-hooks,
    but founds its weakest point was that eventually someone would
    re-clone a repo and make commits with errors before turning
    git-hooks back on.  Another common problem was when we had
    multiple git repositories and git-hooks was only installed in
    some of them, but not all
    
    While it would be nice to be able to use --instalglobal to
    automatically turn on git-hooks on every future repo eventually
    some git repository on github would include a hook that would
    email <secret stuff> back home and all you would have to do
    would be to clone it to activate it which would be a "bad thing",
    but it can pester you without harm.
    
    Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
  3. Behave much better when not in a git repository

    icefox committed Nov 7, 2013
    or when the repository is a bare repository
    
    Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
  4. Add support for Git on windows where find doesn't have the -L option

    icefox committed Oct 24, 2013
    Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Commits on Oct 24, 2013
  1. If git hooks isn't installed explicitly say how to install it

    icefox committed Oct 24, 2013
    Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
  2. In the event we can't rename hooks we should immediately fail.

    icefox committed Oct 24, 2013
    Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Commits on Oct 21, 2013
  1. Fix too many hooks reported in list_hooks_in_dir

    sercxanto authored and icefox committed Aug 24, 2013
    list_hooks_in_dir should report exactly the hooks that would be run with
    run_hooks. But the find command in list_hooks_in_dir does not limit itself to
    the scheme "folder_name/hook_name" but recurses infinitely through sub
    directories reporting all executable files. If your hooks are stored itself in
    a git repository then consequently also the files in .git/hooks are reported.
    
    This change sets the search depth exactly to two, so that the correct scripts
    are reported, e.g. :
        ~/.git_hooks/commit-msg/script1
    
    but not e.g. :
    
        ~/.git_hook/.git/hooks/commit-msg
        ~/.git_hooks/script2
        ~/.git_hooks/commit-msg/dir2/script3
    
    Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>