MediaWiki/Upgrade/REL1 25 to REL1 26: Difference between revisions
No edit summary |
adds simple check for composer.json |
||
| Line 73: | Line 73: | ||
For those [https://gerrit.wikimedia.org/r/#/admin/projects/?filter=mediawiki%252Fextensions%252F extensions available in git] you can fetch the latest updates to the code with something like | For those [https://gerrit.wikimedia.org/r/#/admin/projects/?filter=mediawiki%252Fextensions%252F extensions available in git] you can fetch the latest updates to the code with something like | ||
<source lang="bash"> | <source lang="bash"> | ||
release=REL1_26 | |||
# work within the extensions directory so as not to conflict with the main composer.json | |||
cd extensions | cd extensions | ||
base=`pwd`; | base=`pwd`; | ||
| Line 79: | Line 81: | ||
echo "fetching $ext"; | echo "fetching $ext"; | ||
git fetch; | git fetch; | ||
# checkout the new release branch you want | |||
git checkout $release; | |||
# and update dependencies if project uses composer | |||
if [ -f "./composer.json" ]; then | |||
composer update; | |||
fi | |||
cd $base; | cd $base; | ||
done | done | ||
</source> | </source> | ||
Also, if you don't even know whether there are submodules in use, you can search for those by looking for .gitmodules or .git '''files''' <code>find . -type f -name .git</code> | Also, if you don't even know whether there are submodules in use, you can search for those by looking for .gitmodules or .git '''files''' <code>find . -type f -name .git</code> And if you want to know which extensions may be using composer, you can check <code>find . -maxdepth 2 -name composer.json |xargs grep -l '"require":'</code> | ||
== Preferences == | == Preferences == | ||