title: Git repository organization for a game development
body: <p>We need to develop a game in team and of course the best way is to do it with a git repository. We wonder about how structure it as best for a game development project. In particular a game was made by codes and assets (images, sounds, etc), now those assets need to be developed, for example we should store not just the final image (i.e. PNG) but also the project file for that image (Photoshop, Illustrator...) and this for all assets. 
  Now we can mind some different solutions, for example keep everything in the same repository (divided by folders) [Bad idea, I suppose], split in two repository: one for assets project and the other for the code + asset final, or create a single repository for every asset project.. So there are many many solutions, but what is the best accuracy? Of course the final decision is always directed from team needs, but what are the best/common practices to make a repository for a game?</p>