{"push_id":4292110185,"size":1,"distinct_size":1,"ref":"refs/heads/934-backfill-claim-data-in-geckoboard","head":"0361277cc7cf6dca6a1cf0d9c30cb981637fd7b1","before":"8a61cc68a168cea4bc3eeec0744a34f62e6526a6","commits":[{"sha":"0361277cc7cf6dca6a1cf0d9c30cb981637fd7b1","author":{"name":"Stuart Harrison","email":"c18df0835209cb67c8df8d8e7b67158b67d96e35@gmail.com"},"message":"Add a data migration to backfill claim data\n\nThis way, when the app is deployed, there are two jobs queued to backfill the\nrelevant data. I've added a guard clause to the migration, just in case we\ndecide to do away with the job when cleaning up (we may decide to keep it,\nbecause it's generic enough to be useful for other scenarios if we want to\nbackfill any other types of data in Geckoboard)","distinct":true,"url":"https://api.github.com/repos/DFE-Digital/dfe-teachers-payment-service/commits/0361277cc7cf6dca6a1cf0d9c30cb981637fd7b1"}]}
{"actor":{"display_login":"pezholio"}}