Comments (8)
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.
Related Issues (20)
- Write Documentation HOT 1
- Improve Modularization and Maintenance HOT 3
- Use Test Coverage with pytest-cov HOT 1
- Check flake8 output HOT 1
- Small code improvements HOT 6
- Support xi:fallback element HOT 6
- Add Manpage to Documentation HOT 2
- Enhance Example Section in Doc (fragid/set-xml-id) HOT 2
- Improve error message (trans:idfixup) HOT 1
- Allow referencing to the same document HOT 2
- Support -o/--output option HOT 3
- Support XML Catalogs HOT 2
- Use a declarative approach for setup.py/setup.cfg
- Support inclusion of XML without root node HOT 1
- Validate xi:include attributes HOT 1
- Implement inheriting transclusion attributes HOT 4
- Support -h option HOT 1
- Make version number consistent (0.0 -> 0.1.0) HOT 2
- Catch lxml.etree.XMLSyntaxError Exception HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dbxincluder.