There has long been a hard-coded version number in config.web which only got updated if a diligent developer did so deliberately.
This change replaces that with a version string generated each time you run assemble_here_docs.pl. The version string includes the local date in YYYY-MM-DD format, and a parenthetical revision-control marker pulled from Git.
The revision marker will include:
the Git repository owner's name if it is not herveus,
the branch name if it is not master,
the number of committed revisions in that branch, and
a plus sign if there are un-committed changes in your repository.
As a result, when run in the main branch when everything has been checked into Git, you should generate version strings that look like 2020-09-07 (125), meaning that you're in herveus:master at commit 125.
For comparison, when running in my development branch with uncommitted changes, I am generating version strings that look like 2020-09-07 (mathghamhain:development:154+).
There has long been a hard-coded version number in config.web which only got updated if a diligent developer did so deliberately.
This change replaces that with a version string generated each time you run assemble_here_docs.pl. The version string includes the local date in YYYY-MM-DD format, and a parenthetical revision-control marker pulled from Git.
The revision marker will include:
herveus,master,As a result, when run in the main branch when everything has been checked into Git, you should generate version strings that look like
2020-09-07 (125), meaning that you're in herveus:master at commit 125.For comparison, when running in my development branch with uncommitted changes, I am generating version strings that look like
2020-09-07 (mathghamhain:development:154+).