# Github Dependency Graphs
**URL:** https://discourse.julialang.org/t/github-dependency-graphs/40081
**Category:** Tooling
**Created:** [May 24, 2020, 4:48pm UTC](https://discourse.julialang.org/t/github-dependency-graphs/40081 "2020-05-24T16:48:27Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Ian\_Slagle](https://discourse.julialang.org/u/Ian_Slagle)
#### Post date: [May 24, 2020, 4:48pm UTC](https://discourse.julialang.org/t/github-dependency-graphs/40081/1 "2020-05-24T16:48:27Z")
Currently, to my knowledge, Github’s dependency graphic tool does not work with Julia packages because the manifest is not one of the supported types listed here ([Exploring the dependencies of a repository - GitHub Docs](https://help.github.com/en/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on)). From my understanding of the ecosystem, I feel it wouldn’t be that hard to implement this for Julia packages. What would go into making that happen, and is there interest in doing so?
---
### Author:  [@tbeason](https://discourse.julialang.org/u/tbeason)
#### Post date: [May 24, 2020, 5:21pm UTC](https://discourse.julialang.org/t/github-dependency-graphs/40081/2 "2020-05-24T17:21:21Z")
One issue is that most people do not check in the Manifest.toml for public-use packages. So, you could only go one level deep using the Project.toml files. Perhaps maybe you could do it recursively based on the Project.toml files, but then that seems rather complicated.
---
### Author:  [@Alec\_Loudenback](https://discourse.julialang.org/u/Alec_Loudenback)
#### Post date: [May 24, 2020, 5:44pm UTC](https://discourse.julialang.org/t/github-dependency-graphs/40081/3 "2020-05-24T17:44:34Z")
> [@tbeason](#):
>
> One issue is that most people do not check in the Manifest.toml for public-use packages.
😬 I’m not supposed to do this? I should add `Manifest.toml` to `.gitignore` for my packages?
---
### Author:  [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [May 24, 2020, 5:47pm UTC](https://discourse.julialang.org/t/github-dependency-graphs/40081/4 "2020-05-24T17:47:27Z")
> [@Alec\_Loudenback](#):
>
> 😬 I’m not supposed to do this? I should add `Manifest.toml` to `.gitignore` for my packages?
If you want to have problems with CI every now and then, no 🙂 :troll:
---
### Author:  [@tbeason](https://discourse.julialang.org/u/tbeason)
#### Post date: [May 24, 2020, 6:11pm UTC](https://discourse.julialang.org/t/github-dependency-graphs/40081/5 "2020-05-24T18:11:48Z")
> [@Managing dependencies in packages](https://discourse.julialang.org/t/managing-dependencies-in-packages/34474):
>
> How do I account for package dependencies that vary depending on the Julia version when running CI via travis? My situation: The SpecialFunctions package in its latest version 0.10.0 requires Julia 1.3 or above. When writing a new package that should be supported for Julia 1.0 and above, does that mean I have to resort to the version of SpecialFunctions that supports Julia 1.0 (which is 0.7.2, I believe)? Or is there a way in the Project.toml and Manifest.toml files to support something like i…
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [May 24, 2020, 6:25pm UTC](https://discourse.julialang.org/t/github-dependency-graphs/40081/6 "2020-05-24T18:25:04Z")
[JuliaHub](https://juliahub.com/ui/Packages/Flux/QdkVy/0.10.4?t=1) for example does show dependencies and reverse dependencies for each package in General.