This needs some work to gate off the Run Manually capabilities if not present in Review Board. We don't want to outright crash on 3.0.18 or older.

It's apparent in retrospect, but (and this is probably me being tired) it took too long to realize why we were checking this and bailing. Can we add a comment saying that we're skipping status updates performed by other scripts or extensions?

Probably worth tracking this in Asana with some info on what's wrong.

Maybe worth doing this filtering in _get_matching_configs so we don't compute any more data than we have to?

Got a bunch of thoughts here.
It seems we can get, say, 15 configs here. So:

Each time we get one, we're setting some of the same state on status_update and then saving it, which ideally we wouldn't do (too many hits to the database, unnecessary timestamp updates).
We're also fetching the diff each time. This is going to be the same diff every time, but we're pulling from the database each time.
We're also setting up a session using extension.login_user() above, even if we have zero matching configs returned.

I might be wrong, but I think a better approach would be to have _get_matching_configs() to do the filtering (as mentioned in a prior comment) and then:

if matching_configs:
    repository = ...
    changedesc = ...

    # Fetch the diffset here.
    try:
        ...
    except DiffSet.DoesNotExist:
        ...
        return

    session = extension.login_user()
    ...

    status_update.description = ...
    status_update.state = ...
    status_update.timestamp = ...
    status_update.save(update_fields=('description', 'state', 'timestamp'))

    for ... in matching_configs:
        queue = ...

        extension.celery.send_task(...)

Can we use update_fields= here?

_get_matching_configs() is a generator, so the if check and len and [0] below don't seem like they'd work?

Ship It!