echidna
echidna copied to clipboard
w3c
New publication workflow at W3C — main component
We are unclear about what to do when we hit "deliverer-changed" errors. We have joint deliverables we would like to publish (DAS and WebApps). What do we need to do...
It should be easy for people who read TR specs to cite them correctly. We should generate a bibtex file with citation details for each spec. We could also generate...
Title and ED updates aren't taken into account if the document was already published on the same day
This happened for reporting-1 (see https://github.com/w3c/browser-specs/pull/574).
I wonder if we should consider dropping the Decision URL requirement? As per the new/evolving process, it's pretty much an expectation that we will auto-publish all documents. Maybe we can...
Some of the files have too many callback inditations. e.g. https://github.com/w3c/echidna/blob/main/lib/transition-checker.js#L68
I just learned from the GH support that the list of IPs provided by the API gets updated once a week. https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#ip-addresses This could lead to requests being rejected because...
The [Setting up Echidna as a GitHub hook](https://github.com/w3c/echidna/wiki/Setting-up-Echidna-as-a-GitHub-hook) could probably now point to spec-prod + new instructions.
As discussed in #31. The Symfony endpoint would compare the URL defined initially (when the token was registered) against the URL intended for publication. Only if they are considered equal...
Apart from composing that very long URL, use [GH issue templates](https://help.github.com/articles/creating-issue-templates-for-your-repository/). We can now have multiple issue templates in a repository. And they support pre-filling *labels* and *assignees*, so the...