{"push_id":2341786950,"size":1,"distinct_size":1,"ref":"refs/heads/fix-revision-disorder-1.3","head":"9d0acd79317ebbef1fc7fb6d89ff1cf5b75cb461","before":"f676f295a239393bf36e4e2b85f2c8603f8445e2","commits":[{"sha":"9d0acd79317ebbef1fc7fb6d89ff1cf5b75cb461","author":{"name":"Sandro Santilli","email":"88ec4687d8c7efa69e4ee5795fb7f018e68d4747@kbt.io"},"message":"Avoid incrementing sequence if not needed\n\nThe increment was initially added in an attempt to reduce the risk\nof yet-to-be-committed transactions finding their obtained sequence\nid already used by moved revisions, but the risk was not completely\nremoved and it is only possible to hit this problem when starting\nwith a disordered situation, so better save a gap and eventually\nlet one of the transactions fail on clash.","distinct":true,"url":"https://api.github.com/repos/strk/postgresql-tableversion/commits/9d0acd79317ebbef1fc7fb6d89ff1cf5b75cb461"}]}
{"actor":{"display_login":"strk"}}