Download from Git/sco


 * Sin MediaWiki 1.19beta2, 1.18.2, 1.17.3, MediaWiki core n extensions uise fer version control. Fer aulder versions, see 

Git is distreebutit version control saffware that permits uisers tae doonlaid the fair latest version o ae branch, wioot needin tae wait fer somebodie tae get roond tae packagin it. MediaWiki will release faster, n it'll be easier fer ye tae update yer instawation, row back aen upgrade, or haun patches in. (O coorse aye mynd that offeecial stable releases ar less riskie.)

See Git fer mai details, parteecularlie fer makin contreebutions. Ablo ar some quick directions fer ae few commyn tasks.

Prerequisites
Ye maun hae Git instawed afore ye can uise it. Thaur's monie differant waas tae get Git, dependin oan yer operatin system. Fer soorce n offeecial binaries, see git-scm.com. Fer alternateeve waas tae instaw Git, uise yer faverite rake engine tae fynd instructions fer yer operatin system.

It is recommended that you have Composer installed to download and install third party libraries, but not required.

Doonlaid
Ye can nou doonlaid MediaWiki core (phase3 on SVN) uisin Git, aes weel aes onie extension nou instawed oan the Wikimedia Foondation server cluster. Bi July 2013, aw extensions will either be available uisin Git or muived til alternate version control hosts.

The first step is tae clone the MediaWiki repositrie. This micht tak ae while.

In a terminal window, enter the following command:

This clones the entire MediaWiki core repositrie. The defaut 'branch' will be the cuttin-edge, deveeloper version o MediaWiki. Yince the repositrie is cloned, ye can easilie switch til differant branches or tags (see ablo), incluidin thae trackin stable versions o MediaWiki.

To install into different directory, change that in the command line (for more info refer to these docs). Once the repository is cloned, you can easily switch to different branches or tags (see below), including those tracking unstable versions of MediaWiki. The development branch,, is the cutting-edge, developer version of MediaWiki; you should not use master code for production under any circumstances as it is not considered stable.

If you want to reduce the number of revisions that are cloned, add  to the above command.

The release branches have a bunch of Git submodules in them, for commonly-used extensions and skins (the master branch does not have these). To update the submodules, run:

Download for development
Gif ye'v Deveeloper access (n this is easie tae request), then instead of cloning anonymously with https you should clone with your ssh  so that you can submit changes for review:

This clones the entire MediaWiki core repository, synced to the master branch, into a sub-directory named.



Fetch external libraries
MediaWiki uses Composer to manage external PHP libraries, all of which end up in the  directory in your MediaWiki directory.

To install these needed libraries, you have a choice:


 * Download and install the composer PHAR, optionally rename the composer.phar file as instructed for your OS, and then run  from your MediaWiki directory. This is the recommended approach.
 * Or, if you don't want to use Composer or if you want to use the exact same set of vendor libraries as used on the WMF production cluster, you can instead  to create a   directory inside the core folder of your MediaWiki installation. Note that if any of your extensions have their own Composer requirements, then you cannot use this option.

Prior to MediaWiki 1.25, external libraries were kept in the core repository, and no package manager was required.

MediaWiki tags (stable version)
Alternateevelie, speceefic stable versions o MediaWiki ar trackt uisin 'tags'. Thir ar analogis til the taurbaw releases. Currently, these are (stable),  (LTS) and  (legacy).

You can see all available tags with:

Uisin non GNU sort commaunn, like oan Mac OS X, ye hae tae relie oan the guid auld separaters:

Tae uise ae speceefeec tag:

Latest deveelopmant version o MediaWiki
The latest deveelopmant version o MediaWiki is trackt in the 'maister' braunch. This is whit's locallie checkt oot bi defaut whan ye first clone the MediaWiki repositrie. Gif ye'v switchy til anither braunch bit wid like tae switch back til uisin bleedin-edge MediaWiki, dae:

Keepin up til date
Gif ye'r uisin ae parteecular braunch or the deveelopmant version o MediaWiki, pickin up the latest chynges is reallie easie. Chynge intil yer MediaWiki clone directerie n issue the pul commaunn:

Aw o the latest chynges fer the braunch that ye'r uisin will be applied.

The new version of core may require newer versions of extensions and skins, so you must go into each extension and skin directory and update it with a command like.

You also need to update  with any newer versions of required libraries. This often means running the following Composer command, but see #Fetch external libraries above for more details:

Foreby, efter updatin/upgradin ye shid rin the MediaWiki  fae the commaunn line:

If you use MediaWiki-Vagrant, it offers a single command,, that performs all these steps.

Switchin til ae differant version
Ilka o oor versions ar trackt aes braunches or tags. In order tae switch til yin o thir, aw that ye hae tae dae is 'checkoot' the parteecular braunch or tag that ye want fae wiin yer MediaWiki clone directerie:

or

The chynges will be applied autæmateeclie n ye'll be aw set tae gae.

Uisin Git tae doonlaid MediaWiki extensions

 * List of extensions in git

Doonlaid

 *  shid be replaced wi the name o the extension that ye want tae doonlaid, wiout spaces. Fer Extension:TitleKey, it wid be TitleKey. (case sensiteeve!)

Doonlaid n clone aen extension fae Git:

Deveelopers clone wi:

You can view extension source code in Gerrit's gitiles application, and at the URL:

 https://gerrit.wikimedia.org/g/mediawiki/extensions//+/refs/heads/master

Doonlaid aw extensions
Gif ye prefer tae hae aw MediaWiki extensions that ar at gerrit.wikimedia.org checkt oot til yer machine, dae the follaein:

Tae update the extensions til thair latest versions, jist dae this:

To change to a different branch, such as after a new release:

Remember that you should only use versions of extensions from the same release as that version of MediaWiki and each other.

To track the master branch:

Please note that you should not use master code for production under any circumstances as it is not considered stable.

If you only need a read-only checkout (for instance to grep or analyse all MediaWiki code), you can use the shared MediaWiki checkout on Labs, without downloading anything on your machines.

Remove an extension

 * 1) Remove the " " or " " from
 * 2) Remove any line referencing the extension in   (usually in the "extra → merge-plugin → include" section)
 * 3) Remove the extension's directory in

Using Git to download MediaWiki skins

 * List of skins in git

MediaWiki 1.24 and later don't include skins in the Git download.

Follow the exact same procedure as for extensions (described in the previous section), but using  rather than   in all URLs and paths.

Detailed installation instructions are available on each skin's page here on MediaWiki.org, for example see Skin:Vector#Installation. Instructions for all other skins are analogous.

See ava

 * , aen alternate til doonlaidin fae Git
 * Intranet/Intranet Installation, part of a fully worked series of articles that uses Git for MediaWiki deployment
 * Intranet/Intranet Installation, part of a fully worked series of articles that uses Git for MediaWiki deployment