Report the target branch in subject of committing emails
As a premise, given the amount of commit e-mails flying around, I believe that the information that most helps people visually or automatically filter those e-mail should be the most prominent.
Currently a commit e-mail subject loks like:
[lardataobj] 01/01: add missing header
The vast majority of these e-mails pertains personal feature branches that I believe most of the people are not interested in.
In order to find out, though, one has to open the e-mail and look for the (not so apparent) branch name in its body.
Much better, and target of this request, would be to have the branch information directly in the subject, e.g.
[lardataobj:feature/escudero_PFParticleMetadataMigration] 01/01: add missing header
feature/for brevity: I hope nobody would push a
Also in my experience this Lorena's branch name is quite longer than average, and I expect that normally it would take less space.
#5 Updated by Lynn Garren over 2 years ago
The fnal-git-notify-redmine script uses git-multimail, which is controlled by settings in /cvs/projects/XXX/config on cvmfs.
As a test, I have just added a line to restrict the maximum number of lines to the larsim config.
[multimailhook] .... emailMaxLines = 100
#6 Updated by Lynn Garren over 2 years ago
- Status changed from Under Discussion to Closed
We have looked carefully at the provided options. The header we have now is an informative as possible. Anything else would require expert editing of the python reporting script used by all redmine projects. We did edit the larreco and larsim config files to limit email to 500 lines. This issue is now closed.