Please autodeploy the built spec

[Ms2ger]

CC @bterlson @domenic

[mathiasbynens]

Travis CI could do this, using something like https://github.com/alrra/travis-scripts. See https://github.com/jakearchibald/isserviceworkerready/blob/206c54af0f8eb2b92f8affcc1abdd399c0a72a1d/.travis.yml#L5-L10 for an example.

[mathiasbynens]

Travis CI could do this, using something like https://github.com/alrra/travis-scripts. See https://github.com/jakearchibald/isserviceworkerready/blob/206c54af0f8eb2b92f8affcc1abdd399c0a72a1d/.travis.yml#L5-L10 for an example.

[jakearchibald]

I use that on a few projects & it works great. Means I can even make changes using github's editor on my phone, and the changes get pushed live.

[jakearchibald]

I use that on a few projects & it works great. Means I can even make changes using github's editor on my phone, and the changes get pushed live.

[domenic]

Yeah, I would really appreciate this too; the lag between commits and releases is not really helping anything.

[domenic]

Yeah, I would really appreciate this too; the lag between commits and releases is not really helping anything.

[alrra]

https://github.com/alrra/travis-scripts.

I forked this project in order to show how things would work:

• some of the changes that would be required: https://github.com/alrra/ecma262/commit/fdb71c1341d38e52d8efea528a24d6db15c0680f
  (Note: the favicon.ico, figure-1.png & figure-2.png from the gh-pages branch need to be moved in master and integrated into the build step)
• how a Travis build would work like
• the end result (see also https://alrra.github.io/ecma262/).

@bterlson, @domenic Let me know if you're interested in something like that, and if so, I can open a pull request. The only thing that you would need to do is enable Travis CI for this repository and generate your own secure key.

[alrra]

https://github.com/alrra/travis-scripts.

I forked this project in order to show how things would work:

• some of the changes that would be required: https://github.com/alrra/ecma262/commit/fdb71c1341d38e52d8efea528a24d6db15c0680f
  (Note: the favicon.ico, figure-1.png & figure-2.png from the gh-pages branch need to be moved in master and integrated into the build step)
• how a Travis build would work like
• the end result (see also https://alrra.github.io/ecma262/).

@bterlson, @domenic Let me know if you're interested in something like that, and if so, I can open a pull request. The only thing that you would need to do is enable Travis CI for this repository and generate your own secure key.

[bterlson]

@alrra I would be interested in something like this if you want to send a PR!

[bterlson]

@alrra I would be interested in something like this if you want to send a PR!

[alrra]

if you want to send a PR!

@bterlson Done in #309.

[alrra]

if you want to send a PR!

@bterlson Done in #309.

[bterlson]

It is done.

[bterlson]

It is done.