Deploy devel build of docs to https://nim-lang.github.io/Nim

[kaushalmodi]

To make this PR functional, @Araq or anyone who has admin rights to this repo will need to get the GitHub API token for repo level permissions from https://github.com/settings/tokens. The token will be visible only once. So once you get it, copy it.

Now go to Travis CI settings in a different browser tab, and create an env var named GITHUB_OAUTH_TOKEN (as that's what this PR uses) and paste that copied token value there. Ensure that this env var value is not made public (by default, it's not public).

/cc @LemonBoy

[kaushalmodi]

The sed command in the PR inserts this at the top of the theindex.html page:

[kaushalmodi]

Don't merge this yet. I realized that I can use the TRAVIS_COMMIT env var instead of calculating NIMVER as I do in the PR.

I'll update this PR tomorrow and request a merge again.

[Araq]

Ok, also the entry point is generated from overview.rst and instead of your sed command we can patch nimdoc.cfg to add your note.

[kaushalmodi]

Ok, also the entry point is generated from overview.rst

I didn't follow, so why isn't an index.html being created using that? Not at my computer right now, but if the overview.rst is generating overview.html, should I copy that to index.html instead?

instead of your sed command we can patch nimdoc.cfg to add your note.

I'll have to look at that file to see how to do that.. the 2 dynamic components in that note are the commit hash and the date of publishing. We need to derive those in the nimdoc.cfg then.

[Araq]

Not at my computer right now, but if the overview.rst is generating overview.html, should I copy that to index.html instead?

Yes, I think so.

I'll have to look at that file to see how to do that.. the 2 dynamic components in that note are the commit hash and the date of publishing. We need to derive those in the nimdoc.cfg then.

Not necessarily but you can leave this problem to me.

[kaushalmodi]

@Araq OK, I now copy the overview.html as index.html. I have already removed the sed command. As discussed, it would be nice if you can note the git commit used to generate the documentation somewhere on the page. I see that the footer already has the published time.. may be add the commit hash to it too?

This PR is now ready for merging.