Closed marcoscaceres closed 3 years ago
There are lots of reasons not to push to TR automatically. I'm on holiday so won't take time to elaborate them now. Please don't push any workflow changes to my repositories. I will look at the Travis -> GH actions change when I'm back, but don't plan in the short term to go further than pushing snapshots to gh-pages and would need lots of process coordination to go further.
@michael-n-cooper, no problem - happy for you to handle it. When you are back, please see the email from @plehegar about our service with Travis ending. If you need a hand, just give me a shout! happy to help.
Enjoy your break!!! 🏝
Travis has been disabled on this repository while this gets resolved.
Note that the proposed change uses w3c/spec-proc to push back into the github branch gh-pages
. It does NOT publish into /TR. (Hint: there is no ECHIDNA token in use in the .YML file). See also https://github.com/w3c/spec-prod/blob/main/docs/options.md#gh_pages_branch
Note: I didn't review the changes proposed to the JS code regarding respec. Apparently, the current code is broken and needs fixing. @marcoscaceres kindly introduced the fix in this pull request. This pull request could be split in two if it poses issues (ie one to switch to GitHub action and one to switch to fix the respec JS code).
@michael-n-cooper, I believe this should do the same thing as the .travis script.
Question: any reason not to push to /TR/?
Preview | Diff