Page MenuHomePhabricator

Always use the same set of transactions to generate mail and mail tags
ClosedPublic

Authored by epriestley on Jan 26 2018, 2:55 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 17, 4:45 AM
Unknown Object (File)
Wed, Dec 11, 1:08 AM
Unknown Object (File)
Mon, Dec 9, 2:48 PM
Unknown Object (File)
Thu, Dec 5, 7:55 PM
Unknown Object (File)
Nov 22 2024, 12:46 AM
Unknown Object (File)
Nov 18 2024, 3:33 PM
Unknown Object (File)
Nov 13 2024, 10:44 PM
Unknown Object (File)
Nov 10 2024, 11:07 AM
Subscribers
None

Details

Summary

See PHI307. Currently, when reviews undraft, we retroactively add in older activity to the mail ("alice created this revision...").

However, we don't add that activity to the mail tags, so the relevant tags (like "revision created") are dropped forever.

Instead, use the same set of transactions for both mail body and mail tag construction.

This should be obsoleted in the relatively near future by T10448, but it's a better/more correct behavior in general and we probably can't get rid of tags completely for a while.

Test Plan

Applied patch, created a revision with builds, saw it auto-undraft after builds finished. Used bin/mail list-outbound and bin/mail show-outbound to see the mail. Verified that it included retroactive text ("created this revision") AND retroactive tags.

Note that the tag for "A new revision is created" is DifferentialTransaction::MAILTAG_REVIEW_REQUEST with literal value differential-review-request.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable