Philip Jägenstedt

This bit probably does require admin access to wpt: https://github.com/web-platform-tests/wpt-pr-bot/blob/a56b66951ab92ab1e4594f47d05bc97b8b7f20a1/lib/metadata/status.js#L31-L39

Is the admin role still needed? I think not after https://github.com/web-platform-tests/wpt-pr-bot/pull/22, but it's a bit tricky to audit.

@KyleJu does https://github.com/web-platform-tests/wpt-metadata already support the format for flaky metadata? I search for `flak` in the repo but found nothing.

> I don't think banning spaces in test names is worthwhile. I just searched for spaces in filenames and found two cases that don't seem intentional: https://github.com/web-platform-tests/wpt/pull/46253 https://github.com/web-platform-tests/wpt/pull/46254 Is there...

Tentative tests so far are for things where there's no spec text yet, just an open issue or PR. If we want to be able to link tests to spec...

Often the people being added won't yet be org members so you won't be able to request their review.

I'd like this feature, but would probably avoid it if I was not sure about what the resulting commit message would be, since I like elaborate commit messages. If we...

Squashing for just a single commit is fine too, it'll just append (#XYZ) to the first line, which is kind of handy.

@fantasai Before designing a technical solution, I'd like to try just pushing back against the arguments against test changes you were getting. I think tests should be authored in the...

@stephenmcgruer and @Hexcles (feel free to unsubscribe) put together [WPT and wpt.fyi - inclusive branch naming](https://docs.google.com/document/d/1z9w6i6H3GBkLX4LuwDzbmCHL5U68Dzp9Jfx7Y3Ca4G4/edit) last year, which has much of the detail needed here.