{"push_id":2327661316,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"e6ae0008058fa70bf512fad207b355a19c0280aa","before":"54531f9a004fa86cc0aa43cdd27b3fdff559ce52","commits":[{"sha":"4d94c67d80be499338154902529767790642ce9a","author":{"name":"Harald Sitter","email":"2f4b9dc845d1740f2331f7aed2d3ffa072e14188@kde.org"},"message":"add a new metadata system to get high level access to global metadata\n\nthis is primarily useful to get metadata out of the ISO so we know\nwhat was installed initially.\n\nthis data is uploaded by the install core as soon as possible and later\n(on success) moved to a metdata dir for archival.\nso, for installs the metadata is in ulogs on error and metadata on success\n\nfor !install tests they pick up the metadata from the image storage to\nseed their initial metadata dir (they may still added more info if\napplicable).\nthey always have metadata (from the install), so even on errors we know\nwhat the image contained\n\narchival of this happens relative, so the metadata is in the main dir","distinct":true,"url":"https://api.github.com/repos/apachelogger/kde-os-autoinst/commits/4d94c67d80be499338154902529767790642ce9a"},{"sha":"e6ae0008058fa70bf512fad207b355a19c0280aa","author":{"name":"Harald Sitter","email":"2f4b9dc845d1740f2331f7aed2d3ffa072e14188@kde.org"},"message":"archive the wok relative\n\npreviously we'd have to dig into wok to get to the wok's artifacts, since\nthey are the primary artifacts that is fairly daft though. by diring\ninto the wok first we can archive them into the root of the artifacts dir","distinct":true,"url":"https://api.github.com/repos/apachelogger/kde-os-autoinst/commits/e6ae0008058fa70bf512fad207b355a19c0280aa"}]}
{"actor":{"display_login":"apachelogger"}}