What is the correct method to save non-code related files (reference files/test assets) in a python project?

Viewed 54

From a quick look around; most users have everything in their favorite repository system, which is usually git. Although if you have large files (imagine something like a machine learning dataset or test files used to validate your code, like movie files, images or audio files for example for applications that use them), that is not an option.

Is there a standard to save those "non-code related" files somewhere, and still keep a connection to the main git repo? Since you still need to version your changes for those files, you want something that allow you to create a list of checkin, and probably also a sort of way to save comments with those commits, exactly like you would do with git. Probably would make sense to add also a list of metadata related to those files you check in, so you can retrieve info about them.

I saw that some use 3rd party applications that save assets zipped somewhere, like on AWS or dropbox for example, but that is not feasible for traceability and checkin history, so I assume there is a better way to track files in a project that are not exactly related to code, so they do not really belong in git?

1 Answers
Related