- From: Fuqiao Xue via GitHub <sysbot+gh@w3.org>
- Date: Sat, 27 Mar 2021 11:08:54 +0000
- To: public-i18n-archive@w3.org
xfq has just created a new issue for https://github.com/w3c/clreq: == Use GitHub Actions to build/validate/publish clreq? == https://github.com/w3c/spec-prod is a new, specialized tool that easily automates all steps of building, validating, and publishing specs. To set it up, we just need to add one GitHub Actions file. See [webappsec-credential-management](https://github.com/w3c/webappsec-credential-management/blob/main/.github/workflows/build-validate-publish.yml) for an example. After adding this file, we can autopublish clreq to https://www.w3.org/TR/ , and there's no need to: * use the manifest tool to list items * run the validators * copy remote assets to local repo and update the URLs as part of the publication process for images in the gap analysis (when https://github.com/w3c/spec-prod/issues/32 is fixed) There is a downside: currently, only automatic publishing (on every `git push`) is supported, and manual publishing is not supported. This is tracked in https://github.com/w3c/spec-prod/issues/6 @r12a What do you think? Should we adopt this tool for clreq? What about other lreqs and string-meta / specdev / predefined-counter-styles etc.? (As far as I know, the WebApps, WebRTC, Second Screen, Media, and WebAppSec Working Groups have adopted spec-prod.) Please view or discuss this issue at https://github.com/w3c/clreq/issues/360 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 27 March 2021 11:08:57 UTC