Closed foolip closed 4 years ago
Why Test and not Validate?
It's a test of db.json, sort of :) I went with the same as in https://github.com/whatwg/misc-server/pull/131 which is more like monitoring of production systems.
For more descriptive naming, how about "Workstreams / Validate"? But if we do anything with the markdown files in a workstream of this repo, then we'll have to rename again.
It was a perk of Travis that you didn't need to come up with any names.
Will we use this workflow to run the whatwg.org workflow as well for changes on master?
Not this very workflow file, I'd say, since it should trigger only on push to master. Also, the token provided to a workflow can't cause another workflow to run, so we'll need to do something a bit unusual. Easiest would be to clone whatwg.org and run its deploy script.
(Seems we haven't really enabled much protection here yet. I guess we should.)
I've made "Test" required. Merging this without review from other SG folks because it's just infra, two layers removed from the actual policies and workstreams.
Part of https://github.com/whatwg/meta/issues/173.