Talk:Gerrit/New repositories/Archive 1

Importing an existing extension
I don't understand how to import an existing extension from SVN to Git.

The extension i'm talking about is TranslationNotifications - it has history in SVN and an empty Git repository was created for it, but how is the actual import done? I suppose that a lot of people have this question and i can't find a clear answer here. --Amir E. Aharoni (talk) 06:35, 23 March 2012 (UTC)
 * You bug ^demon and get him to do it. Peachey88 (talk) 07:24, 23 March 2012 (UTC)

Thank you, ^demon, for the link to the list inside the mbox. --Rudolf.Grossmann (talk) 19:56, 30 March 2012 (UTC)

Need to change language
We've got to update the page to reflect
 * it's not just extensions
 * this is for you if your codebase exists but is NOT yet in Git (you need a new repo)

Sumana Harihareswara, Wikimedia Foundation Volunteer Development Coordinator (talk) 21:26, 13 April 2012 (UTC)

Branch model for deployment?
In some time, I'd like to push Extension:Mapsources for review and deployment. It resides at GitHub, and I don't want Change-Ids sprinkled over the commit messages, but of course I am fine with reviews being done in merges.

But I don't see separate deployment branches for various extensions enabled at WMF. Does that mean that reviews of extensions deployed at WMF always happen on the  branch? I'm slightly hesitant with this as this could cause confusion between "GitHub's master" and "Gerrit's master". --Tim&#160;Landscheidt 15:51, 25 September 2012 (UTC)


 * I'm also in a similar situation. Did you figure out the best approach? Sam Wilson 04:00, 31 May 2013 (UTC)

Extensions storing source code on a wiki page.
How to get new repositories created, for moving extensions to? Specifically ones that currently store their source code on a wiki page. Sometimes where the author of the extension is no longer maintaining it. See Pages that link to "Template:Extension code in wiki" for a list of these. --Rob Kam (talk) 09:04, 3 April 2013 (UTC)

add defaultremote=origin to .gitreview?
Soon after someone creates a repository, someone commits a default  to it.

We tell people in Gerrit/Tutorial to add to their own ~/.config/git-review/git-review.conf to avoid possible problems with remotes "origin" and "gerrit" both pointing to gerrit.wm.o. User:VEckl (WMF) and I wonder why the git-repo-creating cabal don't put this in each repo's .gitreview. -- SPage (WMF) (talk) 22:51, 9 July 2015 (UTC)