Page MenuHomePhabricator

Separate revision updates into two separate comments
ClosedPublic

Authored by epriestley on Feb 11 2014, 10:42 PM.
Tags
None
Referenced Files
F17885957: D8200.id18554.diff
Tue, Jul 29, 12:41 AM
F17866480: D8200.id18554.diff
Mon, Jul 28, 4:37 AM
F17850781: D8200.id.diff
Sun, Jul 27, 10:26 AM
F17849885: D8200.diff
Sun, Jul 27, 9:13 AM
F17819006: D8200.diff
Sat, Jul 26, 12:50 AM
F17796634: D8200.id18554.diff
Fri, Jul 25, 1:08 AM
F17794894: D8200.id18551.diff
Fri, Jul 25, 12:02 AM
F17758167: D8200.diff
Tue, Jul 22, 4:55 PM
Subscribers

Details

Summary

Ref T2222. Instead of writing one comment which performs both a diff update and adds a comment, write two comments, one for each action. These will translate directly into ApplicationTransactions writes.

This has a small impact on the UX: these updates now render in two rows, instead of one. After T2222, they'll automerge back together.

{F111909}

Test Plan

Updated a revision.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped