I did some trial and error last week with Twitter via https://cards-dev.twitter.com/validator. That was for my personal blog, but some of it might apply here as well.

See PHI1492. After this change, the parent/subproject modes of the script in T10350 can be brought upstream safely, since they would no longer be destructive operations on membership lists. This wouldn't cover the "convert a project into a milestone" mode, but that seems less important.

1231231

Thanks!

Context isn't automatically unfolding around inlines, but should.

Oh, and maybe lack of source code intraline diffs, although that's likely not too much work.

I think the major remaining issues are:

One broad problem here is "chain of custody" issues in T182. A "Saved State" can easily accommodate multiple representations, and the plan above imagines using Drydock to build tags/branches out of non-repository representations, so we'd have cases where a given "Saved State" has a way to build it with a "patch list" (from the client) or a "ref pointer" (from Drydock).

OIDC is just OAuth2 in a ghost costume, so the implementation is nearly trivial.

Apologies, I should have provided more context. We've been futzing with this project which OIDC. We'd be looking to ensure that it works with Dex.

I'm not sure how I'd even test OpenID these days. Offhand, I haven't seen any provider offering OpenID in years.

Would you considered taking prioritized funding for implementing OpenID?