Page MenuHomePhabricator

Make "first broadcast" rules for Differential drafts more general
ClosedPublic

Authored by epriestley on Nov 28 2017, 6:44 PM.
Tags
None
Referenced Files
F18091049: D18801.id45115.diff
Wed, Aug 6, 6:43 PM
F18090210: D18801.id45103.diff
Wed, Aug 6, 2:51 PM
F18090101: D18801.id45115.diff
Wed, Aug 6, 2:02 PM
F18063208: D18801.diff
Mon, Aug 4, 1:00 PM
F17947298: D18801.id45115.diff
Thu, Jul 31, 4:02 PM
F17847269: D18801.id.diff
Sun, Jul 27, 5:56 AM
F17841488: D18801.id45115.diff
Sat, Jul 26, 10:31 PM
F17836998: D18801.id45115.diff
Sat, Jul 26, 4:48 PM
Subscribers
None

Details

Summary

See PHI228. Ref T2543. The current logic gets this slightly wrong: prototypes are off, you create a draft with --draft, then promote it with "Request Review". This misses both branches.

Instead, test these conditions a little more broadly. We also need to store broadcast state since getIsNewObject() isn't good enough with this workflow.

Test Plan
  • With prototypes on and autopromotion, got a rich email after builds finished.
  • With prototypes off, got a rich email immediately.
  • With prototypes off and --draft, got a rich email after "Request Review".

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable