Philip Jägenstedt

Also, it's probably a good idea to try our workflows while it is in beta, because bugs we report during beta are more likely to be fixed than after it's...

I think there will be challenges with permissions here, and these issues seem to confirm it: https://github.com/actions/labeler/issues/12 To be clear, we wouldn't use https://github.com/actions/labeler anyway, but we have the same...

That would probably work, but I fear that any polling approach would be too slow when it comes to adding labels and reviewers. But maybe wpt-pr-bot could be slimmed down...

The general feedback form for GitHub Actions beta is probably a good place. I would guess that someone is already painfully aware of this, since GitHub Actions was originally tailored...

If we do add docs, https://github.com/web-platform-tests/wpt/issues/18943 would still make it hard to discover.

I'm doing the rotation this week, and https://github.com/web-platform-tests/wpt/issues/14467 was the first that I handled. Quite often I end up changing the priority instead of just nagging. I guess the problem...

Oh, does the Gecko sync bot not use the API for updating metadata then?

Renames are done as part of https://github.com/web-platform-tests/wpt-metadata/blob/master/.github/workflows/update_wpt_manifest.yml, and at least some renaming is happening in https://github.com/web-platform-tests/wpt-metadata/pull/2266

OK, looks like there's a bug. https://github.com/web-platform-tests/wpt-metadata/runs/4506562611?check_suite_focus=true is failing due to dir-style-03a.html not being in the manifest, and must not have detected the rename in https://github.com/web-platform-tests/wpt/pull/31997 correctly.

@KyleJu do you think there have been more deletions like https://github.com/web-platform-tests/wpt-metadata/pull/2260 in the past that we just haven't noticed yet?