Comment 1 for bug 1397481

The way our Zuul configuration is currently written, it looks for the "Jenkins" user leaving a +1 comment as a trigger to enqueue a change into the gate pipeline. Unfortunately this is based on parsing Gerrit comments from the event stream, and leaving a +1 vote in a comment when the same account already has a +1 present results in the +1 not being echoed into the comment text. The workarounds for this are to add another approval vote (workflow +1, removing the existing workflow +1 if needed), or remove the vote from the "Jenkins" account and recheck.