Gerrit/New repositories/de

Diese Seite ist über die Anforderung der Erstellung eines neuen Code-Repositoriums. Alle neue Code-Repositorien sind Git-Repositorien in.

If you want to be a project owner (to be able to review a patch as +2 and merge it) of an existing code repository in Gerrit, see.

Step 0: Evaluation
You may check if you are interested in Gerrit or if you may prefer (available since 2021).

Bemerke, das GitLab es erlaubt, persönliche Repositorien ohne einen formellen Anfrageprozess zu erstellen.



Schritt 1: Git-Zugang erhalten
Access to Git is managed via (LDAP) and integrated with Gerrit. Jeder kann ein Entwicklerkonto erstellen, um Git-Zugang zu erhalten



Schritt 2: Ein Git-Repositorium anfordern
Tell us your wikitech username, which code review model you want (by default this should be "Merge review"), what you want the project name in Gerrit to be (and by implication the path to the project in Gerrit, e.g. ).  Click request, then fill in the fields on the page creation screen: 

Step 3: Commit your files
Once you have some files, you can commit them and continue your work utilizing Git.



Schritt 4: Veröffentlichung einer Erweiterungsseite
To autocategorize and standardize the documentation of your existing extension, please see. To add your new extension to this Wiki:



Vorlagen, die verwendet werden können

 * Extension
 * WikimediaDownload
 * ExtensionInstall
 * Gitweb
 * MW file - verwendet im Handbuch

Step 5: Continue development and enjoy!
You could also try to find a couple of established MediaWiki developers to look over your code and point out any flaws in it, for example by asking on the mailing list.

Getting notified of changes in your repository
Other people may submit patches to your repository which you should review.

You can have new changes in your repository emailed to you by Gerrit. Siehe. If you want to be automatically added as a reviewer to each new patchset (or a subset by regex), add yourself to the Gerrit reviewer bot.



Siehe auch

 * Manual:Extensions - extension or library development guidelines (coding conventions, architecture, license, security, etc.)
 * - Technical instructions for Gerrit administrators who create repositories