Page MenuHomePhabricator

Separate revision updates into two separate comments
ClosedPublic

Authored by epriestley on Feb 11 2014, 10:42 PM.
Tags
None
Referenced Files
F19747094: D8200.diff
Sun, Feb 15, 6:04 PM
F19564317: D8200.id18554.diff
Jan 31 2026, 5:04 PM
F19135457: D8200.id18554.diff
Dec 10 2025, 8:59 AM
F19051517: D8200.id18554.diff
Nov 28 2025, 1:14 AM
F19017470: D8200.diff
Nov 23 2025, 8:03 AM
F19005304: D8200.diff
Nov 21 2025, 3:04 PM
F18992432: D8200.diff
Nov 19 2025, 3:01 AM
F18932812: D8200.id.diff
Nov 10 2025, 9:35 AM
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