Gerrit/New repositories/fr

Cette page concerne la demande de création d'un nouveau dépôt de code. 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.



Etape 0 : évaluation
You may check if you are interested in Gerrit or if you may like more (available since 2021).

Notez que GitLab permet de créer des dépôts personnels sans suivre le processus de demande formelle.



Etape 1 : obtenir un accès Git
L'accès à Git est géré par (LDAP) et intégré à Gerrit. Anybody can create a developer account to get Git access.



Etape 2 : demander un dépôt Git
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. ). Cliquer sur la demande, et remplissez les champs sur l'écran de création de page :



Etape 3 : valider vos fichiers
Once you have some files, you can commit them and continue your work utilizing Git.



Etape 4: publier une page d'extension
To autocategorize and standardize the documentation of your existing extension, please see. Pour ajouter votre nouvelle extension à ce Wiki :



Modèles à utiliser

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



Etre notifié des modifications survenues sur votre dépôt
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.



Voir aussi

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