commit e1153ded6021b24c09b9e31d93e427dc9b695ff1
author Hugo Arès <hugo.ares@ericsson.com> Thu May 17 08:55:30 2018 -0400
committer Gerrit Code Review <noreply-gerritcodereview@google.com> Fri May 18 01:29:11 2018 +0000
tree a3d66faf567ba1fcf6fcaccb217bbc221343c06c
parent b5e620a6a95da453d77f702c1ef8cc77c0e055bf

Update git submodules

* Update plugins/hooks from branch 'stable-2.15'
  to 01c3fb71412e2b0a532e7f9cae389765a8e982ca
  - Merge branch 'stable-2.14' into stable-2.15
    
    * stable-2.14:
      Add submit hook
      Module: Bind listeners in alphabetical order
      Annotate RefUpdate and CommitReceived as Singleton
      Reword documentation of ref-update and commit-received hooks
      Improve hooks documentation structure
    
    Change-Id: I5f5eed398e182c8542b4b53722d942fb2b6bde5a
    
  - Add submit hook
    
    The submit hook is invoked synchronously when a change is submitted. If
    it returns a non-zero exit status, a MergeValidationException is thrown
    and the submit is prevented.
    
    This adds back the ability to block submit by a hook. Previously this
    was possible with the ref-update hook until its purpose was changed and
    only invoked on ref updates such as branch creation, deletion, or fast-
    forward by direct push.
    
    Change-Id: Ie4efb90df645ecac01638b23305dc2ffb547192e
    
  - Module: Bind listeners in alphabetical order
    
    Most of them are already in alphabetical order. Reorder the couple that
    aren't.
    
    Change-Id: I0722c357992bf855baa0a9b8997078036f28cdc8
    
  - Annotate RefUpdate and CommitReceived as Singleton
    
    These should be singletons so that they are not instantiated every
    time a hook is executed.
    
    Change-Id: I32e67a85c24138148c1cff97d76144030942930e
    
  - Reword documentation of ref-update and commit-received hooks
    
    There has been confusion about the purpose of these hooks. Rewrite
    the documentation to hopefully make it clearer.
    
    Change-Id: I86c80072d2d9f05c9d926f0a6a5014590af45b05
    
  - Improve hooks documentation structure
    
    Split synchronous and asyncronous hooks into separate sections, and move
    the duplicated paragraphs about syncronous hook behavior into the top
    of the syncronous hooks section.
    
    Replace legacy section heading formatting (===== and ----- forms), which
    only supports 2 levels, with newer formatting (starting the line with one
    or more # marks) which supports further levels.
    
    Add a table of contents.
    
    Change-Id: Iacf7c44860ec4d77e44c9816fc04ea641a2c8b43