Add another match string to rietveld.go

Add another match string to rietveld.go

BUG=skia:

Committed: https://skia.googlesource.com/buildbot/+/a767b2d8930a9cb8951766cf7bf58fe300f1cfa8

[borenet, 2015-06-23 11:37:40]

borenet@google.com changed reviewers:
+ rmistry@google.com

[borenet, 2015-06-23 11:37:41]

Any idea where I can find the full set of "this was committed" messages that get
generated?  It seems like they're always slightly different.

[rmistry, 2015-06-23 11:48:40]

lgtm

On 2015/06/23 at 11:37:41, borenet wrote:
> Any idea where I can find the full set of "this was committed" messages that
get generated?  It seems like they're always slightly different.

The messages could slightly change whenever somebody adds or removes something,
they are not guaranteed to be constant.
The right way to do this should have been a committed flag that is set in
Rietveld by the different tools but we are unlikely to ever have that because
tight integration between the repository and the code review tool is not
possible here like it is in google3.

The 'as xyz' does not show up for projects that have a hide_ref_in_committed_msg
setting in the CQ.

The first 3 are generated by the CQ and the last one is I believe from
depot_tool's "git cl land".

[borenet, 2015-06-23 12:18:19]

On 2015/06/23 11:48:40, rmistry wrote:
> lgtm
> 
> On 2015/06/23 at 11:37:41, borenet wrote:
> > Any idea where I can find the full set of "this was committed" messages that
> get generated?  It seems like they're always slightly different.
> 
> The messages could slightly change whenever somebody adds or removes
something,
> they are not guaranteed to be constant.
> The right way to do this should have been a committed flag that is set in
> Rietveld by the different tools but we are unlikely to ever have that because
> tight integration between the repository and the code review tool is not
> possible here like it is in google3.
> 

Agree 110%.

> The 'as xyz' does not show up for projects that have a
hide_ref_in_committed_msg
> setting in the CQ.
> 
> The first 3 are generated by the CQ and the last one is I believe from
> depot_tool's "git cl land".

Thanks.  The reason for this CL is that the "AutoRoll failed" alert fired for a
roll which actually succeeded because I didn't have the right message in this
list.  I wish there was a better way.

[borenet, 2015-06-23 12:18:22]

The CQ bit was checked by borenet@google.com

[commit-bot: I haz the power, 2015-06-23 12:18:33]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1193843014/1

[commit-bot: I haz the power, 2015-06-23 12:19:48]

Committed patchset #1 (id:1) as
https://skia.googlesource.com/buildbot/+/a767b2d8930a9cb8951766cf7bf58fe300f1...