Definitions commit info in object_metadata

[gjost]

The object_metadata section on repository objects' JSON files contains the filepath of the ddr-defs file used to write the object, but it does not include the file's Git commit which indicates which version of the file was used. Instead of (or alongside) the file path, we should store the ddr-defs Git origin remote and the commit hash.

UPDATE: Grab the Git info at the time definitions are imported and cache so we're not running git-status on each page save.

[gjost]

Relevant values in the object file "metadata pod":

• app_commit: last commit of ddr-cmdln.
• app_release: version number of ddr-cmdln. This number is not currently being updated - ddr-local/VERSION is the package version.
• defs_path: Absolute path to the ddr-defs module file (not ddr-defs as a whole).
• models_commit: Last commit when the ddr-defs module file was updated.

Note: These values are used in ddr-local to generate those messages about whether document model definitions are SAME/AHEAD/BEHIND.

ddr-local settings.py runs dvcs.latest_commit on the ddr-defs repository (also ddr-cmdln and ddr-local itself) when settings.py is first imported.

ddr-cmdln (which actually writes object metadata files, gets commits for the "metadata pod" at write time.

[gjost]

models_commit was always what we were looking for. Changed to defs_commit to fit current terminology.

Fixed in commit 81f981b