Enable auto-publication #553
Conversation
This automates the publication of all 9 EME documents to the `gh-pages` branch and to /TR, using the w3c/spec-prod action. The `W3CTRMANIFEST` files are no longer needed as a result and nothing needs to be Git-ignored anymore either. Also note the change of shortname for Encrypted Media Extensions to `encrypted-media-2`.
|
Thank you, I have just one question. I notice that /TR/encrypted-media now also shows the FPWD, will both /TR/encrypted-media and /TR/encrypted-media-2 point to the same document as we make more updates? Or should /TR/encrypted-media still point to the existing Rec? |
Yes. I requested the same setting as for MSE: the series shortname
Same as for MSE as well: the previous Recommendation got a (new) |
|
Perfect, that all makes sense. |
|
Will these all run when we change one file? I wonder if we should bind each job to a particular path? |
Yes.
That would be useful for WebCodecs too (16 jobs run whenever a file is changed). It's not trivial because the We could create one workflow per document. That works. That's not DRY-friendly. But then that's simple. Thinking about it, it should be trivial to script the creation of the workflow document to ease maintenance and address the "not DRY-friendly" concern. Or we need to check what changed ourselves within a step. The Paths Change Filter action seems to provide what we need. To avoid starting a new job for each and every document, we would need to drop the "matrix" approach, and rather create one step per document. We'd lose a bit of DRY-ness as well. I'll look into it. Let me know if you see other approaches! |
Automate all the things! This adds an auto-publish workflow template and a companion script to generate auto-publish workflows for each and every spec in the repository that only run when needed, meaning only when the spec source did change. The script only needs to run once in a while when new specs get added or when the workflows need to change. Script and template are in the `.github` folder to avoid polluting the repo with build tools.
|
I created dedicated workflows with |
|
Merging. We can always iterate and improve the workflow afterwards :) |
SHA: cefbd73 Reason: push, by tidoust Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This automates the publication of all 9 EME documents to the
gh-pagesbranch and to /TR, using the w3c/spec-prod action.The
W3CTRMANIFESTfiles are no longer needed as a result and nothing needs to be Git-ignored anymore either.Also note the change of shortname for Encrypted Media Extensions to
encrypted-media-2.I added the Echidna tokens as repository secrets.
Preview | Diff