That command id's files that git doesn't recognize as part of core obtained previously.
I have some bash shell scripts and text files related in /moodlecode/admin/cli/ None of those change core code.
# On branch MOODLE_33_STABLE
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
nothing added to commit but untracked files present (use "git add" to track)
To update ... ie, acquire updates to the version you have ...
git branch -a
At the top:
shows am tracking the 33 branch.
root@sos moodle33]# fgrep '$release' version.php
$release = '3.3.1 (Build: 20170710)'; // Human-friendly version name
git pull would aquire any/all updates to the 33 branch
To upgrade, however, one must issue two commands to track the next highest branch.
# git branch --track MOODLE_34_STABLE origin/MOODLE_34_STABLE;
# git checkout MOODLE_34_STABLE;
Again ... it's important to check if the addons have a compat version. The upgrade process will check and in some cases, might stop your upgrade cold.
This is where a bash shell script using moosh comes in handy.
addons.txt is a simple text file listing the true name of an addon.
The script, checkaddons, reads the lines in addons.txt one at a time, then uses moosh to see what's available for that addon:
echo 'Add-on listing: ';
for i in `cat ./addons.txt`
echo "Addon in que: $i";
moosh plugin-list |grep '^'$i
Again ... IF an addon doesn't have a compat version for the upgraded version you are moving to, it could cause problems - in some cases, major ... like themes.
moosh uses config.php and the moosh command above issued by itself should acquire infor on *all* plugins - even ones you don't have installed.
Output looks like:
The mod/addon workshopeval_weightiest has compat versions for 2.5->3.3. IF I had the addon installed and was upgrading site to 3.3 then that addon should continue to function ... after upgrading it via the Moodle admin UI.
That clear as mud? ;)
Might be a good thing to have a clone of production to test before applying on production server.
Cravat ... if you installed a plugin via git, then you could change into that directory and a git pull there should work like the git pull does with core ... acquires updates to just that plugin ... directory has it's own hidden .git directory.
'spirit of sharing', Ken