Gerrit/GitHub

The authoritative repository for nearly all Wikimedia projects is https://gerrit.wikimedia.org. It is where we conduct code review with software and trigger Continuous integration tests. There is some integration with the commercial service https://github.com.

GitHub mirrors
Most Wikimedia projects are mirrored on GitHub under https://github.com/wikimedia (T37429), e.g.
 * the core MediaWiki software is mediawiki/core in gerrit, with a mirror on GitHub.
 * the is mediawiki/extensions/Flow in gerrit, with a mirror  on GitHub.

You can browse these projects on GitHub and even fork them.

Pull requests for mirrors
Pull requests on GitHub for projects mirrored from Gerrit will be automatically closed by a bot. In order to propose changes to a repository hosted on Gerrit, you will have to create a gerrit change for review from your pull request, or ask someone else to.

Projects on GitHub
Last updated: 2021-06-08 Active GitHub Repos: 169


 * CommonsNotifier
 * CopyPatrol
 * DeadlinkChecker
 * InteractionTimeline
 * KafkaSSE
 * Leaflet.Sleep
 * NYTPhotoViewer
 * OKAPI
 * SurveyCop
 * ToolforgeBundle
 * WhoWroteThat
 * WikiContrib
 * WikidataQueryServiceR
 * WikimediaUI-Style-Guide
 * abstract-wiki-schemata-generator
 * abstract-wikipedia-data-science
 * apiclient-wiki
 * apigateway-rate-limit-tests
 * apps-android-wikipedia-imagerecs
 * articlequality
 * banana-checker
 * banana-i18n
 * browserslist-config-wikimedia
 * bunyan-syslog-udp
 * cassandra
 * change-propagation
 * commtech-musikbot
 * composer-merge-plugin
 * content-type
 * dClass
 * database-reports
 * diff-blog
 * docker-library-images
 * draftquality
 * drafttopic
 * dump-scheduler-eval
 * dumpgrepper
 * editquality
 * edittypes
 * envoy
 * eslint-config-wikimedia
 * eslint-docgen
 * eslint-plugin-mediawiki
 * eslint-plugin-no-jquery
 * eventgate
 * eventmetrics
 * fosdem20webperf
 * fosdem21-web-performance-cfp
 * git-fat
 * grunt-stylelint
 * grunt-tyops
 * hdfs-tools
 * html-metadata
 * htmldumper
 * hyperswitch
 * incubator-superset
 * interconnection-wordpress-theme
 * java-morelangs
 * jmx_exporter
 * jquery.i18n
 * jquery.ime
 * jquery.uls
 * jquery.webfonts
 * json-schema
 * json-stable-stringify
 * jsonschema-compatibility
 * jsonschema-tools
 * kad
 * kartodock
 * kartotherian-tilelive-switch
 * kraken-puppet
 * labs-tools-editorinteract
 * language-data
 * less-plugin-clean-css
 * less.php
 * limitation
 * logstash-report
 * maps-config
 * mediawiki-api-demos
 * mediawiki-docker
 * mediawiki-services-service-runner
 * mediawiki-services-service-template-node
 * mediawiki-title
 * mediawiki-types
 * mw-node-qunit
 * nlwiki_articlequality
 * node-apn
 * node-htcp-purge
 * node-repo-template
 * node-url-get
 * oauth2-server
 * ocean
 * operations-debs-contenttranslation-apertium-af-nk
 * operations-debs-contenttranslation-apertium-api
 * operations-debs-contenttranslation-apertium-hi-ur
 * ores
 * ores-support-checklist
 * ores-wmflabs-deploy
 * ores_bias_project
 * osm-bright.tm2
 * osm-bright.tm2source
 * parsoid-jsapi
 * pcs-html-converter
 * phoenix
 * pi-playbook
 * poppy-cli
 * popularpages
 * preq
 * pretty-json
 * puppet-storm
 * pywikibot-externals-six
 * recommendation-missing-sections
 * recommendation-translation-test
 * research-api-endpoint-template
 * research-api-interface-template
 * research-babel-parser
 * research-datasets
 * research-gapfinder-analytics
 * research-gapfinder-gadget
 * research-navigation-vectors
 * research-reader-survey-analysis
 * research-similar-users
 * research-translation-recommendation-models
 * research-translation-recommendation-predictions
 * research-wmf-utils
 * resource-modules
 * restbase
 * restbase-mod-table-cassandra
 * restbase-mod-table-mysql
 * restbase-mod-table-spec
 * restbase-mod-table-sqlite
 * revscoring
 * riemann-jmx
 * service-runner
 * service-template-node
 * simplei18n
 * skinomatic
 * sqoopy
 * stylelint-config-wikimedia
 * subversion-svn.wikimedia.org-trunk
 * svgtranslate
 * swagger-router
 * takedown-tools
 * thank-you-note
 * tools-globalsearch
 * twcs
 * typescript-types
 * waxer
 * webpagetest
 * wikibase-changes
 * wikidiff2-docker
 * wikilabels
 * wikilabels-wmflabs-deploy
 * wikimedia-android-data-client
 * wikimedia-logo
 * wikimedia-ocr
 * wikimedia.github.io
 * wikimediafoundation-org
 * wikipedia-android-lite
 * wikipedia-ios-Tweaks
 * wikipedia-ios-codemirror
 * wikipedia-ios-lite
 * wikipedia-ios-liter
 * wikipedia-kaios
 * wikipedia-preview
 * wikipediapreview-wordpress
 * wikitax
 * wmfdata-python
 * ws-export

Setting up the GitHub triangular workflow
This is a guide on contributing to Wikimedia's Gerrit-hosted projects with a GitHub-based workflow. This guide is aimed mainly at Windows-based users that use GitHub for Windows (GitHub Desktop), but should also be usable for contributors who work from the console. However, for this last group, contributing using is probably easier.

In this guide, 'm using the pywikibot repository as an example, but the same workflow can be applied to any repository hosted in WMF's Gerrit. The GitHub for Windows workflow has some issues (notably GHfW reporting an error while pushing).

The normal GitHub workflow is as follows:
 * 1) Clone from the original repository
 * 2) Push to your own repository
 * 3) Submit a pull request

We will set up this using GitHub for Windows:

Cloning the repository

 * 1) Go to
 * 2) Click 'Clone in Desktop'

GitHub desktop will now launch, and clone pywikibot, including all submodules.

Forking the repository

 * 1) Go to
 * 2) Click 'Fork'

A fork is now created under your GitHub username, e.g.

Setting up push options
We now want to configure git to pull from the central repository and to push to your own repository (https://github.com/&lt;username>/pywikibot). For this, follow these steps:


 * 1) In GitHub for Windows, click tools » open a shell here
 * 2) In this shell, type these commands:
 * 3) git config remote.origin.pushurl https://github.com/&lt;username>/pywikibot.git
 * 4) git config remote.origin.push +refs/heads/*:refs/heads/*

The first command configures your own GitHub repository as place to push, the second sets 'force push' as default - this will result in your fork to be always equal to what you have locally in GitHub for Windows.

Submitting a patch

 * 1) Make some changes
 * 2) In GitHub for Windows, click 'master' and type a branch name in the 'Filter or create new' field. Press Enter to create it.
 * 3) Select files to commit and press 'commit'
 * 4) Press 'publish'. Your changes are now pushed to your own repository on GitHub.
 * 5) Browse to
 * 6) Under 'Your recently pushed branches' click 'Compare & pull request'
 * 7) Add a note, then click 'Send pull request'

Updating a patch

 * 1) Make some changes
 * 2) Commit to the relevant branch
 * 3) Click 'sync'
 * 4) If you get an error message, click tools » open a shell here, and run  'git push'. This should always succeed.
 * 5) The change is automatically added to your pull request

Other GitHub organizations
It's a mess! Here are a few of the existing Wikimedia-focused group repositories.
 * https://github.com/wikimedia
 * https://github.com/mediawiki-utilities
 * https://github.com/countervandalism
 * https://github.com/cssjanus
 * https://github.com/oojs
 * https://github.com/toolforge
 * https://github.com/toollabs
 * https://github.com/tool-labs
 * https://github.com/wiki-ai
 * https://github.com/Wikidata
 * https://github.com/Wikidata-lib
 * https://github.com/WikidataQuality
 * https://github.com/DataValues
 * https://github.com/wikimediadc
 * https://github.com/wikimedia-research
 * https://github.com/wmde
 * https://github.com/WoCUG

See also https://github.com/MWStake/nonwmf-extensions for a super-repository of MediaWiki extensions not hosted at Wikimedia.

Plus countless personal repositories.