Follow-up to, https://archives.gentoo.org/gentoo-dev/message/9e875b528eee3732e2c1ff34b791006d It would be helpful if, when a git hook modifies a bug, it CCs the committer who triggered the edit. There are several "open" maintainers, for example maintainer-needed and sci*, where it's acceptable to make drive-by commits as a non-maintainer. Often a bug assigned to those addresses will get closed by a commit hook, and someone will later comment on the fix -- as in, "thanks," or "it's still broken on x86." If the committer doesn't remember to CC himself on the bug, he'll miss that comment. Automating the process is less error-prone, and avoids sending everyone an extra email upon the box being checked. The main technical detail to work out is how to avoid CCing the committer twice, if he's already CCed via an alias. For this it may suffice to loop through projects.xml, since only developers can be the committer (as opposed to the commit author). That isn't a bullet-proof solution, but getting an extra email every once in a while due to a corner case is also not a huge deal.
> The main technical detail to work out is how to avoid CCing the committer twice, > if he's already CCed via an alias. ^ AFAIK ago has that worked out. CCing ago, any help?
(In reply to Joonas Niilola from comment #1) > > The main technical detail to work out is how to avoid CCing the committer twice, > > if he's already CCed via an alias. > > ^ AFAIK ago has that worked out. CCing ago, any help? Hi, atm I'm just CC'ing when the assignee is different from the committer. This helps in visibility expecially when people organizes mails from alias into a different directory. To avoid double-cc (or double mail) I see two possibilities: 1) Have an API that should be called at runtime 2) Store the alias somewhere on the machine, but it may be out of sync at some time.
