Greg Hurrell

Let me give you a concrete example of what this change would mean for me (just one data point). At my job we have about a dozen repos currently following...

> Easy. And really, that's it. Both sides will be okay, plus the tooling and the parsers. I think you might be overstating the ease here. Sure, `parse-commit-message` can (already)...

`` > CC is in an interesting position. It's a spec for both the tool authors and for the regular users which is just writing commits. Is it that different...

Interesting discussion. Thanks for starting it @OlegIlyenko. As you know, the role of directives as [currently defined in the spec](https://facebook.github.io/graphql/#sec-Language.Directives) is pretty narrow; they are intended to: > [D]escribe alternate...

I think I'd like to see us do the same thing we've done with some other projects that Facebook either runs or is involved in: - https://yarnpkg.com/ - http://facebook.github.io/jest/ Basically,...

Thanks for doing all that work @jonirrings. My thinking on this is still like I [said above](https://github.com/graphql/graphql.github.io/issues/173#issuecomment-316474358) — that using a mature, third-party translation platform is the ideal end state...

Those `setTimeout` are coming back to haunt us, @julien. 😂 @p2kmgcl: do you have a stack trace?

> * Should this be a local command we run or a gh action? My suspicion is that anything related to liferay-portal isn't really suitable for a GitHub action, because...

Closed by: https://github.com/liferay/alloy-editor/pull/1394 Released in: https://github.com/liferay/alloy-editor/releases/tag/v2.11.7 liferay-portal PR currently running against CI here: https://github.com/wincent/liferay-portal/pull/277

@julien: I created this one so we can build up a list of stuff that needs to be in place so that we can make the most of @mwilliams2014 involvement...