575 posts Magento Elite & Gravity Maker
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • United States
  • Has been a member for 4-5 years
  • Referred between 50 and 99 users
  • Bought between 1 and 9 items
  • Exclusive Author
GravityDept says

I’ve been doing research on this and opinions seem pretty divided. If you’re using git to track development of your products, what are you keeping in the repo besides code?

Icons? Small images? PSD, FW-PNG, or AI files? Fonts? I’m not talking about content images, but any binary assets you might need to deploy the site or get a new developer’s environment set up. You’d need everything right?

Are there realistically problems with the repo bloating, or rebasing crashes on binaries? Any thoughts are appreciated.

367 posts
  • Elite Author
  • Sold between 250 000 and 1 000 000 dollars
  • Most Wanted Bounty Winner
  • Europe
  • Referred between 50 and 99 users
  • Exclusive Author
  • Bought between 10 and 49 items
+1 more
pixelgrade says

Hi. We keep just the theme on github. The rest of the assets go to Google Drive.

17 posts
  • Author had a File in a Mini Bundle
  • Europe
  • Has been a member for 1-2 years
  • Exclusive Author
  • Sold between 10 000 and 50 000 dollars
  • Referred between 10 and 49 users
  • Bought between 10 and 49 items
prestahome says

Just use Dropbox or GDrive. Git is not an option for files like .psd, .jpg, why? For example – you can’t merge image files. I am using Git for theme and Dropbox for all of assets and “Start project” files.

575 posts Magento Elite & Gravity Maker
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • United States
  • Has been a member for 4-5 years
  • Referred between 50 and 99 users
  • Bought between 1 and 9 items
  • Exclusive Author
GravityDept says

What if you need to compare two releases?

Seems like it would be tedious and error-prone to match up the binary assets to GDrive / Dropbox manually. Those systems also wouldn’t tell you when an asset changed, and you’d essentially be storing copies for every release. That wouldn’t really be any different than just keeping a folder of all your releases zipped up (which I already do).

The main reason for putting all assets into git would be collaboration. If you have several developers making changes to icons, for example, you might need to revert at some point or trace what has changed. Without the source files in version control it’s really possible to manage that across different developer’s computers.

1024 posts Best-dressed man at PressNomics 2013
  • Attended a Community Meetup
  • Author had a File in an Envato Bundle
  • Bought between 1 and 9 items
  • Contributed a Tutorial to a Tuts+ Site
  • Exclusive Author
  • Has attended an Envato Live event
  • Has been a member for 5-6 years
+5 more
Parallelus says

We keep just our themes in a Github repo. Dropbox has been our shared file storage but I’m probably going to try something else. I’m not very impressed by Dropbox. All I ever really notice about it is the limitations.

491 posts
  • Elite Author
  • Sold between 250 000 and 1 000 000 dollars
  • Won a Competition
  • Referred between 1000 and 1999 users
  • Author had a Free File of the Month
  • Author had a File in an Envato Bundle
  • Bought between 10 and 49 items
+3 more
pixelentity says

Everything but psd files, they would pollute the git repo too much imho.

by
by
by
by
by
by