Jump to content

Topic on Talk:Download from Git

Sophivorus (talkcontribs)

According to Download from Git#Keeping up to date, to do a minor update from, say, MediaWiki 1.39.1 to 1.39.3, I should do the following:

git pull
composer update --no-dev
php maintenance/update.php

This I do, and all goes well. However, after a successful update, I'd expect that running git status should yield an empty report (no unstaged changes, no untracked files), but it doesn't. Instead, I see all bundled extensions listed as unstaged changes, and all non-bundled extensions listed as untracked.

The first list I usually resolve by running:

git submodule update --init --recursive

Should this be added to Download from Git#Keeping up to date?

And what about the non-bundled extensions that appear listed as untracked? Is this expected? Shouldn't the extensions directory be included in .gitignore or something? What's the proper way to do a minor update?

Bawolff (talkcontribs)

It depends a little bit on how you're using git. If you are following tags, you would need to change to the 1.39.3 tag first. If you are following a release branch, then git pull would work.

I would recommend git pull --recurse-submodules if using a release branch so it automatically updates submodules.

Extra extensions you added being untracked is to be expected. Perhaps extensions other then bundled ones should be added to .gitignore, but that is not currently done at this time.

Reply to "Proper way to update"