Enable using gh-pages branch for displaying the spec
#22
Assignees
Comments
|
Yes, I think we need someone with admin access to the repo to set that up. |
|
@yoavweiss should have access to enable GH pages. |
|
Done!! :) |
Merged
mingyc
added a commit
to mingyc/pending-beacon
that referenced
this issue
Aug 29, 2022
* Removed `index.html` from `main`. Now it's auto-generated from `index.bs` and put into `gh-pages` branch. Available at https://wicg.github.io/unload-beacon/ * Fixed broken super-linter badge. Related: WICG#22
Merged
mingyc
added a commit
that referenced
this issue
Aug 29, 2022
* Removed `index.html` from `main`. Now it's auto-generated from `index.bs` and put into `gh-pages` branch. Available at https://wicg.github.io/unload-beacon/ * Fixed broken super-linter badge. Related: #22
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've created the
gh-pagesbranch, but it looks like this repo is not enabled to use it for https://wicg.github.io/unload-beaconNot quite sure about the process here, but given that we already have a spec file (although it's not up-to-date with the explainer), should we enable the static page?
I also have a PR ready to setup github workflow to generate the update from *.bs file.
The text was updated successfully, but these errors were encountered: