github.com/grantbow/fit@v0.7.1-0.20220916164603-1f7c88ac81e6/fit/Bug.Close-should-be-able-to-notify-people/vcs-hook-git-multimail (about)

     1  Flexibility to embed fit in other systems sounds great. The described
     2  bug.Close() would be one way to implement this feature.
     3  
     4  This powerful feature may be better implemented in other ways, either at the
     5  VCS level or separately.
     6  
     7  Questions naturally arise about how this would work depending on how it is
     8  implemented. The right implementation should be at an appropriate level of
     9  abstraction so as not to artificially exclude alternative implementations.
    10  
    11  For example a file containing a list of email addresses in each issue directory
    12  could be read and used only for changes to that issue.
    13  
    14  Projects may not find this highly ineffective. Projects often rely on
    15  notifications across whole projects, not just single issues. People in projects
    16  may use the email notifications in many different ways.
    17  
    18  A git plugin run during the post-receive hook exists: git-multimail.py
    19  
    20  This is a tool distributed with git and developed at
    21  https://github.com/git-multimail/git-multimail
    22  
    23  The recommended implementation is a python override of
    24  get_revision_recipients() as described on line 2555 of
    25  https://github.com/git-multimail/git-multimail/blob/master/git-multimail/git_multimail.py
    26  as of release 1.5.0.
    27  
    28  The git-multimail/post.receive.example file has just such python overrides.
    29  
    30  If a python implementation is not desired a configurable exerimental feature
    31  multimailhook.refFilterInclusionRegex is part of git-multimail.py. It matches
    32  against complete refnames and could match against just issue path names.  The
    33  git-multimail/README.rst describes features "multimailhook.refFilter(*)Regex"
    34  for Inclusion, Exclusion, DoSend and DontSend settings.
    35  
    36  github and other systems built on top of VCS have their own notification
    37  systems which may be adequate.
    38  
    39  There are available workarounds and alternative ways of handling email
    40  notifications. Please share your solutions.
    41