{"push_id":898821448,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"8c77a1ec2a33906a4446638ffd8ff783285f7fee","before":"d46b7cc15d552fcbb7c2ded46a92a704caedbe79","commits":[{"sha":"8c77a1ec2a33906a4446638ffd8ff783285f7fee","author":{"email":"1455a6109f174a5d555c9262c6fc8e2160d1c4fa@gmail.com","name":"kcdodd"},"message":"Changed user access authorization\n\nA guest account is now created for every visitor to the app, which can\nact just like a regular account, but which cannot be logged into by\nusername or password, and will lose authorization at the end of a\nbrowser session (ie close tab). But if a user logs in while the guest\naccount is still active, everything made with the guest account will be\ntransferred to the user that logs in.\n\nThere are now only two ways to grant access to a rout. Either add the\nuser directly to the access list of the route, or add a group to which\nthe user is a group to the route. The permissions can be placed either\nper route, or by the type of route (safe/unsafe/update, etc), but not\nboth. the root access also grants full access to the resource (like the\nowner option did). But there is no longer a true 'owner' of a resource,\nonly access permissions. The route restrictions are also available on\nthe client side so the client can know what can be accessed.","distinct":true,"url":"https://api.github.com/repos/kcdodd/broadsword/commits/8c77a1ec2a33906a4446638ffd8ff783285f7fee"}]}