github.com/driusan/bug@v0.3.2-0.20190306121946-d7f4e7f33fea/issues/Bug.Close-should-be-able-to-notify-people/vcs-hook-git-multimail (about)

     1  Flexibility to embed bug in other systems sounds great. The described
     2  bug.Close() would be a nice place to implement this feature.
     3  
     4  A step towards implementing this would be reconmmending a convention to help
     5  other developers with whatever implementation they choose. For example a file
     6  containing a list of email addresses in each issue directory could be read and
     7  used only for changes to that issue.
     8  
     9  This seems like it couild also be implemented together with whatever standard
    10  VCS mechanisms already exist though the Description states implementing it
    11  independently of the VCS.
    12  
    13  I don't know about hg or other VCS but a git plugin run during the post-receive
    14  hook exists: git-multimail.py
    15  
    16  The recommended implementation of this is a python override of
    17  get_revision_recipients() as described on line 2497 of
    18  https://github.com/git/git/blob/master/contrib/hooks/multimail/git_multimail.py
    19  
    20  The file post.receive.example has just such python overrides.
    21  
    22  If a python implementation is not desired configurable exerimental a feature
    23  multimailhook.refFilterInclusionRegex of git-multimail.py hook. It matches
    24  against complete refnames and could match against just issue path names.
    25  
    26  github and other systems built on top of VCS have their own notification
    27  systems.
    28  
    29  Given the available workarounds this feels like a lower priority than other
    30  features and may be better handled in a different way. I encourage anyone
    31  interested to try this out.
    32