-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy changes to policy files to whatwg.org #110
Comments
Given that there's a human involved in merging PRs, going to https://github.com/whatwg/whatwg.org/commits, clicking the checkmark, going to the Travis CI build, and rerunning it, doesn't seem overly onerous given the number of changes. It might help to see a diff of the generated HTML though in case of further Markdown/CommonMark issues. |
I suspect this can be fixed more easily after whatwg/meta#173 (at least the part of sg changing causing whatwg.org to rerun). |
This is to make it easier to run the same deploy steps from whatwg/sg#110, without pinning a version in two places. (But it would still duplicate some stuff.)
After I landed #129 I tried to get it deployed by restarting the latest workflow run on push to master, which resulted in https://github.com/whatwg/whatwg.org/runs/779420751?check_suite_focus=true However, that doesn't seem to have worked, and I don't know why. If merging whatwg/whatwg.org#333 also doesn't deploy the changes then something weird is going on. |
This is to make it easier to run the same deploy steps from whatwg/sg#110, without pinning a version in two places. (But it would still duplicate some stuff.)
Oops, false alarm, I had an entry in my /etc/hosts for whatwg.org for testing whatwg/misc-server#129. |
This is half of the solution, in addition the sg repository will need to trigger the event: https://developer.github.com/v3/repos/#create-a-repository-dispatch-event Part of whatwg/sg#110.
This is half of the solution, in addition the sg repository will need to trigger the event: https://developer.github.com/v3/repos/#create-a-repository-dispatch-event Part of whatwg/sg#110.
Currently it's the build/deploy step of https://github.com/whatwg/whatwg.org that converts the Markdown files in this repository to HTML and publishes it to whatwg.org. It works when it runs, but updating just the files in this repo doesn't trigger that deploy process.
See #88 (comment) for a recent example.
The text was updated successfully, but these errors were encountered: