Gerrit/Neue Repositorien

This page is a translated version of the page Gerrit/New repositories and the translation is 31% complete.

Outdated translations are marked like this.

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

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 Gerrit/Privilegrichtlinien .

Step 0: Evaluation

You may check if you are interested in Gerrit or if you may prefer GitLab (available since 2021).

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

Schritt 1: Git-Zugang erhalten

To commit and review Git commits, we use Gerrit. You can login to Gerrit using your Wikimedia developer account.

Jeder kann ein Entwicklerkonto erstellen, um Git-Zugang zu erhalten

Schritt 2: Ein Git-Repositorium anfordern

You'll need the following:

Wikimedia developer account

Repository name – Decide on an appropriate repository name (and by implication, its parent namespace in Gerrit), e.g. mediawiki/extensions/Example). Check the list of existing repository names.

Phabricator project

– This is where tasks about your repository should be reported, e.g. MediaWiki-extensions-Example.
If you don't have one yet, then submit your request for a Phabricator project first.

Request new repository

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 Vorlage:Erweiterung . To add your new extension to this wiki:

Vorlagen, die verwendet werden können

{{Erweiterung }}
{{WikimediaDownload }}
{{ExtensionInstall }}
{{Git repo }}
{{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 wikitech-l 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 Gerrit/watched projects 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

Handbuch:Erweiterungen - extension or library development guidelines (coding conventions, architecture, license, security, etc.)
Git/Creating new repositories - Technical instructions for Gerrit administrators who create repositories