[Elchi3]

Adds the spec for mdn/content#187

[Elchi3]

(side note: the CI error message is very unhelpful and there was no error locally).

[chrisdavidmills]

This looks good. I'll merge this now.

[chrisdavidmills]

Ah wait, I can't because the commit is not signed. @peterbe is this because @Elchi3 needs to set up signature verification, a la https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/about-commit-signature-verification ?

[chrisdavidmills]

I guess I ought to do that too, in that case

[Elchi3]

I had signed commits set up previously but forgot to do it again after I pruned my laptop. Grr.

The Yari repo has no contributing.md nor seem to mention this anywhere, fwiw.

[chrisdavidmills]

I used to do it via SSH keys, but it looks lke GH doesn't support those any more? I'll go learn about GPG ;-)

[escattone]

@Elchi3 So good to "see" you my friend! I'll merge this for now.

[Elchi3]

Thank you, Ryan! ❤️ Looking forward to talking more :)

[peterbe]

For now, the mdn/yari repo requires signed commits but the mdn/content repo does not. Ideally, we should require it everywhere but the assumption is that there'll be a lot more people who come to mdn/content and they might not have it set up. Clearly, this is happening.
One of the risks of not requiring signed commits is security in that you might be fooled to trust a commit when you think it comes from a trusted colleague/friend when in fact it's not. That might make you merge things without looking carefully, and that actor might be sneaking things in. This is a risk factor for both repos but more so for mdn/yari because its code is directly connected to our AWS production account which ultimately can build out pages that have direct access, on the same domain, to the production database.

I think we should consider it a warning for contributors. A manual warning (ie. no GitHub PR bot).
"Hey, you should ideally use signed commits. Read here about how to set it up. It's actually easy. But I took an extra careful look at your changes and they seem perfectly fine. Thanks!"