Pascal Birchler

Here's some hacky bash code I put together the other day to retrieve all warnings by WP-CLI (and filter out false positives caused by https://github.com/wp-cli/i18n-command/issues/154): https://github.com/google/web-stories-wp/blob/fc38c6e046e90c8b48fd5ef410a8a45d6ff02078/.github/workflows/lint-i18n.yml#L113-L142 Maybe it's helpful.

I don‘t think anyone is currently working on this. Pull requests are more than welcome!

GitHub Actions are also very interesting. I got my invite today, so perhaps I can explore it a bit soon :-)

Object sub types (e.g. custom taxonomies): Hmm, we could do `sanitize_key()` in `\Core_Sitemaps_Provider::get_sitemap_url`, but then we also need to do it in places using `\Core_Sitemaps_Provider::get_object_sub_types` Object types (e.g. custom providers):...

Hmm... Something like that is certainly doable, but I don't particularly like it. Especially since I would not want to support this for non-Bitbucket-requests

We had some discussions on Slack about this: https://wordpress.slack.com/archives/CTKTGNJJW/p1592319614495500

Thanks for this issue! First and foremost, only the REST API infrastructure is being merged into WordPress 4.4. Endpoints are probably coming with 4.5 because they still need need some...

If there isn't already an action for that, we can definitely add one that is being run when the cache gets refreshed. Adding a custom endpoint for that sounds like...

WP Spider Cache is interesting too.

Thanks for your input @Geschan! So basically you suggest turning the "No cache generation by logged in users" checkbox into an option where you could say e.g. "Only enable caching...