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
F15377317: D16846.id40568.diff
Thu, Mar 13, 8:36 AM
F15375886: D16846.id.diff
Thu, Mar 13, 12:31 AM
F15335720: D16846.id40568.diff
Sat, Mar 8, 5:28 PM
F15332225: D16846.id40565.diff
Fri, Mar 7, 4:51 PM
F15319842: D16846.id40568.diff
Thu, Mar 6, 9:30 PM
Unknown Object (File)
Tue, Feb 25, 6:07 AM
Unknown Object (File)
Feb 9 2025, 11:31 AM
Unknown Object (File)
Feb 9 2025, 11:26 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