{"push_id":856963336,"size":1,"distinct_size":1,"ref":"refs/heads/dir-transmat-uri-support","head":"f337a5252c6af10e0e300a16e6a70affad882164","before":"d24ee6597f32e03c0b90480b8225c4d54ec01e99","commits":[{"sha":"f337a5252c6af10e0e300a16e6a70affad882164","author":{"email":"2346ad27d7568ba9896f1b7da6b5991251debdf2@exultant.us","name":"Eric Myhre"},"message":"Fix one (1) ton of dir transmat legacy behaviors:\n\n- data locations are now URIs!  (like everyone else, finally)\n- data locations can be content-addressible!  (like everyone else, finally)\n- multiple commit locations for an output are supported.  (like everyone else.)\n- arbitrarily deep directories will not be created for output.  (like everyone else.  it's sanity preservation in the event of fat-fingering.)\n- commits are transactional!  (tmpdirs are used correctly, and atomically moved into place.)\n  - except if you're using non-CA mode.  because that's impossible within the limits of posix filesystem's atomicity primitives.  As if you needed yet another reason to go full-on CA...\n\nOverall, this goes a long way towards bringing the dir transmat back in line with \"what you'd expect\" if you're accustomed to the config of any of the other supported core transmats, and makes it easier to swap out (e.g. s/tar/dir/ for the type, and it'll work now... as you'd expect).\n\nSigned-off-by: Eric Myhre <hash@exultant.us>","distinct":true,"url":"https://api.github.com/repos/polydawn/repeatr/commits/f337a5252c6af10e0e300a16e6a70affad882164"}]}