New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 726410 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Jul 2017
Cc:
jrn@google.com
█ jparent@chromium.org
█ sop@google.com
charliea@chromium.org
█ logan@google.com
estaab@chromium.org
mar...@chromium.org
rmis...@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Support review for GitHub repositories

Project Member Reported by aga...@chromium.org, May 25 2017 
Right now, multiple projects (e.g. luci, catapult) use Rietveld to review changes to repos which are homed on GitHub.

We either need to unilaterally declare that they move to Gerrit instead of GitHub, or we need to have a system in place for changes reviewed on Gerrit to be pushed to GitHub.

Comment 1 by mar...@chromium.org, May 25 2017

Cc: estaab@chromium.org
For github.com/luci, I think we have a general consensus about migrating to gerrit. There's a partial discussion there
https://groups.google.com/a/google.com/d/topic/chrome-infra/A7j8VXUXx6Q/discussion
but I think most of the discussion occurred on IM.

Comment 2 by aga...@chromium.org, May 25 2017 

Fantastic, I've filed a bug here (https://bugs.chromium.org/p/chromium/issues/detail?id=726507) for switching luci to be homed on Gerrit.

Still need to figure out the best path forward for catapult and any other Rietveld+GitHub repos we discover.

Comment 4 by aga...@chromium.org, Jul 25 2017

Mergedinto: 529026
Status: Duplicate (was: Available)
Merging this into the "support mirroring" bug, since that is our chosen approach.
►

Sign in to add a comment