New issue
Advanced search Search tips

Issue 690092 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 631551
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug


Previous locations:
gerrit:5501


Sign in to add a comment

Need a way to request CQ

Project Member Reported by jochen@chromium.org, Feb 8 2017

Issue description

In the webkit code review tool, you could mark a CL as requesting CQ, i.e., if the reviewer was entirely happy with your patch, they knew that it was OK to not only mark it as reviewed, but also dump it into the CQ.

There should be a way to mark a CL as such in gerrit as well
 
Owner: andyb...@chromium.org
Andy, this is not a Gerrit issue, this is specific to the Chrome workflow. Is there a Chrome project it can be moved to?
in the dogfooding email, we were asked to file issues in this component.
Thanks for the info, I will take my objections to agable.
Cc: aga...@chromium.org
Owner: ----
As part of triage of PolyGerrit issues, we’ve just been moving them to the Chromium project in the case where it’s Chromium-specific. This has scaling issues as we onboard more people, so we’ll follow up off-bug.
Project: chromium
Moved issue gerrit:5501 to now be  issue chromium:690092 .
Components: Infra>Codereview>Gerrit
Labels: -Priority-3 Pri-3
Status: Available (was: New)

Comment 7 by aga...@chromium.org, Feb 13 2017

Labels: Milestone-Afterglow Proj-Gerrit-Migration
This is clearly afterglow, as it is a regression relative to the WebKit tool, not to Rietveld. Also, I think it might actually be a gerrit feature request (adding an "autosubmit" capability), but we'll come back to that after launch.
Labels: -Milestone-Afterglow
Removing Milestone-Afterglow, as it has ceased to have meaning. More refined milestones may be added back in the near future.
Mergedinto: 631551
Status: Duplicate (was: Available)

Sign in to add a comment