Re: [ALL] Change to GitHub Workflow message subjects

2023-10-05 Thread sebb
On Thu, 5 Oct 2023 at 17:48, Mike Drob wrote: > > But often [VOTE] and [RESULT] are send with the same otherwise subject (and > sometimes even [DISCUSS] before the vote, on other projects) However in that case the merged conversations will at least relate to the same component. I have not persona

Re: [ALL] Change to GitHub Workflow message subjects

2023-10-05 Thread Mike Drob
But often [VOTE] and [RESULT] are send with the same otherwise subject (and sometimes even [DISCUSS] before the vote, on other projects) On Thu, Oct 5, 2023 at 11:43 AM sebb wrote: > On Thu, 5 Oct 2023 at 17:25, Gary Gregory wrote: > > > > Should we use (VOTE) instead of [VOTE]? > > I doubt tha

Re: [ALL] Change to GitHub Workflow message subjects

2023-10-05 Thread sebb
On Thu, 5 Oct 2023 at 17:25, Gary Gregory wrote: > > Should we use (VOTE) instead of [VOTE]? I doubt that is necessary. The GMail behaviour particularly affects the Workflow messages because the same workflow names are re-used, so often the only differentiator was the [component_repo] e.g. [GitH

Re: [ALL] Change to GitHub Workflow message subjects

2023-10-05 Thread Gary Gregory
Should we use (VOTE) instead of [VOTE]? Gary On Thu, Oct 5, 2023, 10:53 AM sebb wrote: > I discovered recently that GMail conversation mode ignores certain > subject prefixes when deciding which emails are in the same thread. > > In particular, it ignores text in [brackets]; as these were used

[ALL] Change to GitHub Workflow message subjects

2023-10-05 Thread sebb
I discovered recently that GMail conversation mode ignores certain subject prefixes when deciding which emails are in the same thread. In particular, it ignores text in [brackets]; as these were used to enclose the repo name, this resulted in merging emails from different components. The email su