You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, w3c/spec-prod only accepts respec|bikeshed for TOOLCHAIN. We have groups, like w3c/epub-specs that trigger echidna publication without invoking respec|bikeshed. One possibility would be to skip the uild step if TOOLCHAIN=AS_IS (or something like that)
The text was updated successfully, but these errors were encountered:
Support a no-op build wouldn't be difficult/out of scope, but I'm curious to know why w3c/epub-specs builds static snapshots from ReSpec documents, adds them to git and then publishes them; instead of generating/publishing them on the fly. It might be a good chance to replace the current system?
Right now, w3c/spec-prod only accepts respec|bikeshed for TOOLCHAIN. We have groups, like w3c/epub-specs that trigger echidna publication without invoking respec|bikeshed. One possibility would be to skip the uild step if TOOLCHAIN=AS_IS (or something like that)
The text was updated successfully, but these errors were encountered: