One recurring problem I've noticed in dealing with the Package Manager is that we need to occasionally share a list of all the packages we have installed and what versions they are. For example, my colleague installed "Riley Labrecque - Steamworks" locally through the Package Manager and pushed changes for related work. However, on my end, because I have not repeated the installation step, I recieve compiler errors relating to the Steamworks package being absent. In worse situations, this can lead to stuff being silently broken or bugged out on some workstations because they aren't using the same package versions. For example, another developer made a level in ProBuilder. When I pushed changes to the level containing the ProBuilder meshes, all of his meshes vanished on his worstation when he pulled my changes. It appears that the two versions of ProBuilder were fighting over how to serialize the mesh data into the scene. It is also very tedious and error prone to ensure that all relevant packages are installed with the same versions across workstations. Ideally, it should be the case that when someone updates or installs a package, they can push this on Git. When other developers pull, any added or updated packages will also be pulled in. However, I'm not sure what folders should be unignored by .gitignore, or how to otherwise safely use Git to syncronize the state of the Package Manager. Also worth noting: I moved the Post-Processing folder to the Packages folder (next to Assets) so that I could modify the post-processing shaders. I asked about this on these forums previously and this is the current workflow for package development. Ideally, packages that are moved here and the changes made to them should be synced via Git as well. What is the currently accepted practice for doing this? Thanks!