Page MenuHomePhabricator

Don't let users write summaries or test plans which will become ambiguous in commit messages
ClosedPublic

Authored by epriestley on Nov 12 2016, 3:14 PM.
Tags
None
Referenced Files
F18866112: D16846.diff
Mon, Nov 3, 3:29 PM
F18817435: D16846.id.diff
Tue, Oct 21, 3:35 PM
F18813829: D16846.id40565.diff
Mon, Oct 20, 7:10 PM
F18812417: D16846.diff
Mon, Oct 20, 9:12 AM
F18807154: D16846.id40568.diff
Sat, Oct 18, 11:30 PM
F18806808: D16846.id40568.diff
Sat, Oct 18, 9:39 PM
F18790849: D16846.id40565.diff
Wed, Oct 15, 8:06 PM
F18777544: D16846.diff
Sat, Oct 11, 3:34 AM
Subscribers
None

Details

Summary

Ref T11085. To recreate the issue:

  • From the web UI, click "Edit Revision".
  • Write something like this as your "Summary" (i.e., put another field marker, like "Test Plan:", into the summary):

This is a test of the
Test Plan: field to see
if it works.

  • Save changes.

Later, when the summary is amended into a commit message, the parser will see two "Test Plan:" fields and fail to parse the message.

Instead, prevent users from making this edit.

Test Plan

Screen Shot 2016-11-12 at 7.10.43 AM.png (846×2 px, 112 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable