WebKit exports remain open

[foolip]

I just approved and merged #18756, but that should have been handled by the WebKit export process. Exports for WebKit changes that have landed in WebKit should be merged, and any abandoned ones should be closed.

There are also many WebKit exports without the webkit-export label, so it seems like some script isn't applying the label when it should be. Maybe this is a permission problem though?

[foolip]

Note that I've manually added the webkit-export label to a bunch of PRs now, so the linked query will be empty or have just a few PRs.

[foolip]

A related problem has also occurred, where the export PR has been closed without being merged:
#13606 (comment)

In either case the tests haven't ended up in the wpt repository.

[foolip]

Turns out those changes were exported in another PR: #13805 (comment)

@youennf given that there can be multiple WebKit commits for a single bug, I wonder if there's any bookkeeping or audit script to ensure that no changes are accidentally lost in either direction? https://crbug.com/754619 is a Chromium issue about auditing our import/export process, but we haven't prioritized it. Still, @Hexcles may have ideas for how such an audit would work. Whether it's likely to discover bugs in the WebKit tooling I dare not speculate.

[foolip]

@zcorpan has filed https://bugs.webkit.org/show_bug.cgi?id=203359 consistently adding the label.

[foolip]

@rniwa this is the issue I mentioned at https://webkit.org/meeting/ with strange things happening with WPT exports. #18756 was one case.

[stephenmcgruer]

I'm downgrading to backlog because nobody appears to own driving this forward (the assignee has never commented on this), but cc @clopez who has recently been doing work on the export process.