Yarik

Yeah, I figured out it is intended to be this way. I'm not sure if it has any downsides or performance hits for the database

Related to: https://bugzilla.mozilla.org/show_bug.cgi?id=1880386

Related to #3652

The order of [github events](https://docs.github.com/en/webhooks-and-events/webhooks/webhook-events-and-payloads?actionType=closed#pull_request): * `push` event for a commit(s) * `pull_request`.`opened` event * force push commit or add new -> `push` event * `pull_request`.`synchronize` event (head of branch...

hey @jonalmeida thanks for reminding about this issue :) Yeah, I think we can close it unless you have some evidence it is still not working. We've done so many...

let's merge this?

Another angle to this problem is using [mozilla-history](https://github.com/taskcluster/mozilla-history/blob/master/main.go) for this purpose. We are already "tracking" most of the entities this way (except secrets) by scraping them and storing in git...

@petemoore this is probably fine to remove, can you reabase to see what tests would fail? I think none of them should

I will close this one, commented in the ticket

@petemoore somewhat yes I believe, we are going to make it possible to see what tasks are pending, so they can be later shown in the UI as well