Gerrit/New repositories

This page is about requesting the creation of a new code repository. All new code repositories are Git repositories 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).

Note that GitLab allows to create personal repositories without a formal request process.

Step 1: Get Git access
Access to Git is managed via (LDAP) and integrated with Gerrit. Anybody can create a developer account to get Git access.

Step 2: Request a Git repository
You'll need the following:
 * Wikimedia developer account,
 * Decide on an appropiate repository name (and by implication, its parent namespace in Gerrit), e.g. ).
 * Phabricator project, or see creating new project to request a new one.

Request new repository

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

Step 4: Publish an extension page
To autocategorize and standardize the documentation of your existing extension, please see. To add your new extension to this Wiki:

Templates to use

 * Extension
 * WikimediaDownload
 * ExtensionInstall
 * Gitweb
 * MW file - used in the Manual

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. See. 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.