# How to store the set of needed packages in git

**URL:** https://discourse.julialang.org/t/how-to-store-the-set-of-needed-packages-in-git/31975
**Category:** General Usage
**Tags:** question
**Created:** [December 7, 2019, 3:47pm UTC](https://discourse.julialang.org/t/how-to-store-the-set-of-needed-packages-in-git/31975 "2019-12-07T15:47:47Z")
**Posts on this page:** 1
**Page:** 2

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [December 8, 2019, 7:43am UTC](https://discourse.julialang.org/t/how-to-store-the-set-of-needed-packages-in-git/31975/21 "2019-12-08T07:43:08Z")

</div>

I think that one should always commit the `Manifest.toml` to repositories — for registered packages it is innocuous (in the sense that the registry will ignore it), while it can be invaluable when you need to know a set of versions that is known to work. Then you can bisect from there to debug the occasional bugs that come from unexpected/undocumented API changes.

[Previous page](https://discourse.julialang.org/t/how-to-store-the-set-of-needed-packages-in-git/31975.md?page=1)