Deploy Documentation on GitHub Pages about dbxincluder HOT 8 CLOSED

It should limit the build for the master and develop branches only

Isn't it either-or? Wouldn't the documentation for develop overwrite the documentation for master if both branches are specified?

from dbxincluder.

Isn't it either-or? Wouldn't the documentation for develop overwrite the documentation for master if both branches are specified?

Good catch. Probably yes. The question is, if we want it.

My assumption was that both are (should be?) useful. When you create a release on master, it should overwrite anything that was deployed on develop before. On the other side, if you change anything in develop, it will be also published (assuming the there are doc changes).

If we allow publishing only on master, documentation is not always up-to-date. Depends probably on how often we create a release.

I'm open for suggestions. :)

from dbxincluder.

I wonder if is possible with travis-sphinx to upload the documentation into a subdirectory on gh-pages.
I doubt that though, as that sounds like it breaks down with concurrent builds.

from dbxincluder.

I wonder if is possible with travis-sphinx to upload the documentation into a subdirectory on gh-pages.

As far as I know, I don't think this is possible.

from dbxincluder.

IMO it makes sense to only deploy documentation of the master branch.
Those using the develop branch either don't need the documentation or are able to build it manually.

from dbxincluder.

I'll implement this after there is a generatable documentation in the master branch.

from dbxincluder.

Sounds good to me. 👍

from dbxincluder.

Fixed, now with a clean usable design: https://opensuse.github.io/dbxincluder

from dbxincluder.