{"push_id":1339561237,"size":1,"distinct_size":1,"ref":"refs/heads/dev","head":"65ead2b00fc319116238b3baa83b89b946ab0c12","before":"cd33f82ed67b4ce12f47ec4c52d193bf6b169472","commits":[{"sha":"65ead2b00fc319116238b3baa83b89b946ab0c12","author":{"name":"Matt Galloway","email":"31e7b35f7f9f5d76c1e2ef239c79b97264b2f6d0@galloway.me.uk"},"message":"Fix saving when the content hasn't actually changed\n\nSee #31. There was a problem where if you saved when the content hadn't actually changed, then there was an error. Of course it's not actually an error, but rather the content hasn't changed, so there's nothing to save. This could happen if you moved something to the left and then back again. With undo/redo now it's more likely to happen, so important to fix. This fixes it.","distinct":true,"url":"https://api.github.com/repos/mattjgalloway/emoncms-dashboard/commits/65ead2b00fc319116238b3baa83b89b946ab0c12"}]}
{"actor":{"display_login":"mattjgalloway"}}