{"push_id":2312419482,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"60906f6e6690f7d7fc23eb65ecfdb718aeb2da60","before":"cb169cc43c5e11ac7124ed7a636c22327ef6a1eb","commits":[{"sha":"60906f6e6690f7d7fc23eb65ecfdb718aeb2da60","author":{"name":"Duncan Garmonsway","email":"9837da98fa81d2e67e6ac0991f12f8a7f52a7c73@digital.cabinet-office.gov.uk"},"message":"Use generic 'parent' field. (#193)\n\nAgreed with the technical architect, that hierarchies will be common, so it will\r\nbe better to define one generic 'parent' field as a CURIE, rather than lots of\r\nparent fields that are register-specific.  Custom field descriptions will\r\nexplain to users what the field represents in each context.","distinct":true,"url":"https://api.github.com/repos/openregister/registry-data/commits/60906f6e6690f7d7fc23eb65ecfdb718aeb2da60"}]}
{"actor":{"display_login":"nacnudus"}}