Recently I’ve been exploring the “Dependency graph” feature.
I think it’s really cool and helpful feature, but I have 2 remarks/questions about it which I was unable to resolve/find answers for anywhere on the Internet… One short, and one longer.
It seems that the page: https://help.github.com/articles/listing-the-projects-that-depend-on-a-repository/ is outdated, because it contains a note: “Note: The Dependents graph only contains data for Ruby gems and doesn’t include data for other languages or Git submodules.”. I can clearly see the dependency graph working for Python projects as well. Is it not supposed to work for Python, actually?
Some of the dependencies in the dependency graph are properly linked to their respective repositories, while some others are not linked. Those not linked ones appear kinda grayed out, and have a generic icon. (specifically, this one: )
For example, even though my repositories are listed properly as dependents of a given project: https://github.com/simonpercivall/astunparse/network/dependents?dependent_type=REPOSITORY when I go to list packages that depend on the very same project: https://github.com/simonpercivall/astunparse/network/dependents?dependent_type=PACKAGE I see all of my packages and few others as grayed out.
Also, as far as dependencies are concerned, for all of my projects (as far as I checked, at least), in the dependency graph, if a given dependency is my other project it is also grayed out. It also happens for few other projects. However, I can still explore the sub-dependency graph for those grayed out dependencies in some cases. E.g. https://github.com/mbdevpl/transpyle/network/dependencies
As a project owner, is there any way for me to fix that? I’d like my projects to be properly attributed and linked to their repos in the dependecy graph.