Enable auto-publication of the spec to /TR #146
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This update enables auto-publication of the spec as Candidate Recommendation Draft to /TR, as agreed by the working group. It leverages the [spec-prod action](https://github.com/w3c/spec-prod/) to do that. This update also adjusts the workflow for the Editor's Draft itself. The source spec is now to be found in the `main` branch, and instead of publishing the source spec to GitHub Pages directly, the spec-prod action will rather deploy the generated spec. Among other things, this makes it possible to integrate the spec in Bikeshed's database for cross-referencing purpose (fixing w3c#137). The spec-prod action also takes care of running ReSpec on pull requests to validate changes from an editorial perspective. Note the `ECHIDNA_TOKEN` was added as secret to the repository.
ReSpec requires a `crEnd` date when the spec's status is CR or CRD. It makes sense for CR (the date appears in the Status of this Document section). It does not really make sense for CRD (the date does not appear anywhere). Anyway, adding the parameter to please the ReSpec and make the auto-publication process succeed.
A `<dl>` cannot be used without `<dt>`. Switching to `<ul>` instead to contain the list of conditions. Needed to enable auto-publication since the spec-prod action validates the HTML.
|
Looks like things are working smoothly. Thank you again @tidoust! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update enables auto-publication of the spec as Candidate Recommendation Draft to /TR, as agreed by the working group. It leverages the spec-prod action to do that.
This update also adjusts the workflow for the Editor's Draft itself. The source spec is now to be found in the
mainbranch, and instead of publishing the source spec to GitHub Pages directly, the spec-prod action will rather deploy the generated spec. Among other things, this makes it possible to integrate the spec in Bikeshed's database for cross-referencing purpose (fixing #137).The spec-prod action also takes care of running ReSpec on pull requests to validate changes from an editorial perspective.
Note the
ECHIDNA_TOKENwas added as secret to the repository.Related PR for the Presentation API: w3c/presentation-api#502
Preview | Diff