-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with submodules (using mkdocs-monorepo-plugin) #23
Comments
Right, I'll have a closer look and try to implement a similar mechanism. |
Thank you! I started thinking if in the future it would make sense to have a shared |
As of now, the plugin doesn't support submodules. I opened a ticket on the GitHub project for the plugin: Guts/mkdocs-rss-plugin#23
@timvink has already imagined this scenario for his plugins and I've proposed to integrate the RSS plugin along the others. See: timvink/mkdocs-git-authors-plugin#16 (comment) |
Yup, common utils for accessing git for mkdocs files would be better. Very low on my priority list though and needs to be well designed.. feel free to pick it up! |
This is used to work around the following issue with the RSS plugin: Guts/mkdocs-rss-plugin#23.
Hello,
I started using mkdocs-rss-plugin but noticed that at the moment it's not compatible with mkdocs-monorepo-plugin. When I run
mkdocs build
I get the following output letting me know that the plugin couldn't find the dates for files in the submodules (in this case, the ones insidesubmodules/chart/
):Since this plugin is based on the plugins by Tim Vink (which I'm also using), I checked how those plugins work and they determine the local Git repository for each file before using Git to obtain the metadata on the file, as seen here:
https://github.com/timvink/mkdocs-git-revision-date-localized-plugin/blob/d4303ad2efd4d4cda49116d8e8bdb0aa5012d4d3/mkdocs_git_revision_date_localized_plugin/util.py#L91
Would you be willing to implement the same mechanism on mkdocs-rss-plugin to make it compatible with submodules?
The text was updated successfully, but these errors were encountered: