{"push_id":1091073812,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"fe545ec5bd9fefbc05ada61a5a3b1a1189fc8bf4","before":"a21c179f6ecec95e575dbc938a0e846b1528a9b0","commits":[{"sha":"fe545ec5bd9fefbc05ada61a5a3b1a1189fc8bf4","author":{"email":"136f0e76c84dc95d95c03f432ac7ba4a3dc9c6b7@users.noreply.github.com","name":"not-an-aardvark"},"message":"Fix an issue where requests wouldn't be ratelimited after reset warnings\n\nPreviously, if the `config().continue_after_ratelimit_error` option was set to `true` and multiple requests were queued after the ratelimit was exceeded, they would all be immmediately carried out as soon as the current ratelimit period expired, rather than being throttled according to the `config().request_delay` option. This fix addresses the issue by putting the throttling logic after the ratelimit checks, rather than before.","distinct":true,"url":"https://api.github.com/repos/not-an-aardvark/snoowrap/commits/fe545ec5bd9fefbc05ada61a5a3b1a1189fc8bf4"}]}