Skip to content
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

Keep the published editors draft in sync with master #70

Open
adob opened this issue May 18, 2017 · 6 comments
Open

Keep the published editors draft in sync with master #70

adob opened this issue May 18, 2017 · 6 comments

Comments

@adob
Copy link
Contributor

adob commented May 18, 2017

The index.bs and index.html files are continually updated in the master branch but the changes don't routinely make their way over to the gh-pages branch and published docs at https://w3c.github.io/webappsec-suborigins/index.html.

The result is that the draft is out of date. Is this intended? Can we keep gh-pages and master in sync?

@devd
Copy link
Contributor

devd commented May 18, 2017

I just pushed. It isn't intended per se but it isn't an invariant we try to maintain either: I am ok with it being a little out of date. But will try and do a better job keeping it in sync! sorry about that.

@devd devd closed this as completed May 18, 2017
@annevk
Copy link
Member

annevk commented May 18, 2017

Why are they different though?

@devd
Copy link
Contributor

devd commented May 18, 2017

ohh its just easier to review the diff with .bs than all the changes to index.html. Further, sometimes people can make changes in the github UI and don't run bikeshed. Updating it as simple as running make and make publish on the checkout from the console. Haven't cared enough to have a cron job doing this in the background. Is this something that already has a good solution?

@annevk
Copy link
Member

annevk commented May 18, 2017

For WHATWG we have an automated setup that publishes from Travis. I think @domenic can offer some advice on how to do it for GitHub pages.

@annevk annevk reopened this May 18, 2017
@domenic
Copy link

domenic commented May 18, 2017

@devd
Copy link
Contributor

devd commented May 18, 2017

ok. I will try to get to this. if anyone else has the time, feel free to grab this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants