Thursday 15 January 2015

git - Should I commit media files to my github repo? -



git - Should I commit media files to my github repo? -

i start using github store projects i'm sort of confused media files. many of projects have been working on single page web applications have heavy utilize of graphics create projects nice. i'm torn because if commit , force projects without graphics looking @ code (a possible employer) might confused , think project visually ugly or worse, find broken images everywhere since gitignored image files. however, if commit , force graphics seems might viewed not best practice , bloat repository. tried doing git pages 1 time , confused graphics.

most of projects i've seen on github don't seem web applications more not plugins , libraries don't have clue other people doing problem. there standard or best practice way of dealing git files images?

in general, since git tracks content (any content), not care add together repository. whether it’s text files (e.g. source files), compiles binaries or other binary assets images. internally, git handles in same way.

you should think whether graphics part of repository or not. way describing it, seems indeed part of project since other files depend on them. furthermore, cannot created files nowadays in repository (e.g. compiled binaries not included since repository contains source compile them).

as “bloat”, yes, binary files larger text documents. such, having many binary files in repository can increment size of repository. don’t have impact compared text files. applies text files applies binaries: since git stores each content of file 1 time (regardless of type), file stays same throughout history stored once. if graphics constant (i.e. not changing them time), absolutely not end “bloating up” repository.

and again, if part of project, should part of repository.

git github

No comments:

Post a Comment