Skip to main content
added 801 characters in body
Source Link
Dan
  • 7.6k
  • 6
  • 54
  • 123

I'm managing my Unity 2019.3 project in git and I have a directory called Packages in the root of my project. In here there is a file called manifest.json. Is this the only file that matters in the folder or are there other configuration files that could be generated and need tracking?

In other words, is it safe to put the following lines in my .gitignore

/[Pp]ackages/*
!/[Pp]ackages/manifest.json

This is very similar to this question but it doesn't explicitly answer what I want to know.


Edit

To clarify, I am asking if manifest.json will always be enough to regenerate the content of Packages or if there may be other files that are stored in there and required for configuration. I.e. files that won't be the same if left for automatic regeneration by Unity.

The use of this is I have an asset that adds files to that Packages folder and they do not need tracking. They are automatically added back in by the asset when needed. So I want to exclude all but the necessary files from that folder. If the necessary files could change and there is no way for me to know what configuration files could be generated, then I will not do this. If manifest.json is going to always be the only file of importance in that folder, I will leave my .gitignore as it is.

I'm managing my Unity 2019.3 project in git and I have a directory called Packages in the root of my project. In here there is a file called manifest.json. Is this the only file that matters in the folder or are there other configuration files that could be generated and need tracking?

In other words, is it safe to put the following lines in my .gitignore

/[Pp]ackages/
!/[Pp]ackages/manifest.json

This is very similar to this question but it doesn't explicitly answer what I want to know.

I'm managing my Unity 2019.3 project in git and I have a directory called Packages in the root of my project. In here there is a file called manifest.json. Is this the only file that matters in the folder or are there other configuration files that could be generated and need tracking?

In other words, is it safe to put the following lines in my .gitignore

/[Pp]ackages/*
!/[Pp]ackages/manifest.json

This is very similar to this question but it doesn't explicitly answer what I want to know.


Edit

To clarify, I am asking if manifest.json will always be enough to regenerate the content of Packages or if there may be other files that are stored in there and required for configuration. I.e. files that won't be the same if left for automatic regeneration by Unity.

The use of this is I have an asset that adds files to that Packages folder and they do not need tracking. They are automatically added back in by the asset when needed. So I want to exclude all but the necessary files from that folder. If the necessary files could change and there is no way for me to know what configuration files could be generated, then I will not do this. If manifest.json is going to always be the only file of importance in that folder, I will leave my .gitignore as it is.

Source Link
Dan
  • 7.6k
  • 6
  • 54
  • 123

Version control of packages in Unity 2019

I'm managing my Unity 2019.3 project in git and I have a directory called Packages in the root of my project. In here there is a file called manifest.json. Is this the only file that matters in the folder or are there other configuration files that could be generated and need tracking?

In other words, is it safe to put the following lines in my .gitignore

/[Pp]ackages/
!/[Pp]ackages/manifest.json

This is very similar to this question but it doesn't explicitly answer what I want to know.