-
Notifications
You must be signed in to change notification settings - Fork 71
Open
Labels
type:bugSomething isn't workingSomething isn't working
Description
I'm attempting to switch to sphinx-multiversion, but I've run into an issue that I don't think there is an existing solution for. If there isn't, I'm curious if this is something you'd be willing to support and how you'd like it implemented.
I have a project where the code is in one repository and the sphinx docs source files are in another. The docs repository is included in the code repository as a git submodule. So you have something like:
myrepos/
mypkg/
__init__.py
doc/ <-- git submodule
conf.py
I'd like sphinx-multiversion to take the tags and branches it uses from the code repository (myrepos/), but because doc/
is also a git repository itself sphinx-multiversion is only using the ones defined there. Is it possible to make sphinx-multiversion look one level up for the main repository?
taironemagalhaes
Metadata
Metadata
Assignees
Labels
type:bugSomething isn't workingSomething isn't working
Type
Projects
Status
Backlog