What should one do with media assets related to a Git repository?

Question

Some of the simple examples of GitHub practice will include addition or deletion of code in HTML/CSS files.

However, what should one do with media assets (which may be central to a web app)? Is it feasible or worthwhile to use Git and/or GitHub to store media assets such as images, or even video? What's considered best practice?

After reading this Stack Overflow post, it seems to me that Git can possibly store some kind of acknowledgement that they exist as part of a project. In addition, this link gives some good tips for dealing with assets.

What should I do with those assets?

Answer 1

It looks like nowadays assets or media data can be handled using DVC (Data version control system): https://dvc.org/ to keep repositories nice and thin (or at least under required size limitation).

Answer 2

This information on Stack Exchange was helpful

It seems that some people are proponents of using submodules within git, or even creating a separate repository for images/assets. Some say using a third party like Dropbox can help, or Unison. Others find it necessary to include assets in version control.

As far as I can see, uploading assets to a Git Hub repo wont degrade images so there is no reason not to, within the recommended 1gb limit.. To conclude, as with most things, it all depends on your requirements and circumstances at the time.

Answer 3

It is definitely possible to use Git Hub as a cloud for your media content. I don't think it's against their terms of service since you are utilizing their tools. The only thing that concerns me is your privacy. Your content will be accessible by thousands of users across the internet.