Michael Kaye 8607397ea7 Make a ":latest" tag, and a SHA1 commit ID one too. ... Latest is horrible and makes debugging what has happened anywhere a nightmare. We push a latest because of demand for it, but we'll also push a SHA1 commit id so those wanting to know what they're running (and be able to roll back if required) can use those instead. Note that latest here is defined as "most recent master commit" not "most recent released version", as the actual semantics of making latest correct while still being able to build bugfixed releases of previous versions is just ARGH. So we define it as "master" not "latest release".		2018-09-27 12:01:41 +01:00
..
config.yml
merge_base_branch.sh