After doing a git pull of your repo into my fork to obtain recent changes (for the past 3 months or so), I tried to push the changes to my repo onto github and
and received the following error:
remote: Error code: cf3ef3ca01dcb4e333ad0b07914beb75
remote: warning: Error GH413: Large files detected.
remote: warning: See http://git.io/iEPt8g for more information.
remote: warning: File stars/layers/stars.dbf is 64.68 MB; this is larger than GitHub's recommended maximum file size of 50 MB
remote: error: File colorize-alpha/layers/fire_ca.dbf is 316.57 MB; this exceeds GitHub's file size limit of 100 MB
To https://github.com/skorasaurus/tilemill-examples.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/skorasaurus/tilemill-examples.git'
As of June, github no longer allows files larger than 100mb. (Also see: https://help.github.com/articles/what-is-my-disk-quota)
To fix this, perhaps just throwing those files onto Amazon cloud S3 and making a .gitignore file to remove them and/or hardcode the url into the projects to trigger a download.
After doing a git pull of your repo into my fork to obtain recent changes (for the past 3 months or so), I tried to push the changes to my repo onto github and
and received the following error:
remote: Error code: cf3ef3ca01dcb4e333ad0b07914beb75
remote: warning: Error GH413: Large files detected.
remote: warning: See http://git.io/iEPt8g for more information.
remote: warning: File stars/layers/stars.dbf is 64.68 MB; this is larger than GitHub's recommended maximum file size of 50 MB
remote: error: File colorize-alpha/layers/fire_ca.dbf is 316.57 MB; this exceeds GitHub's file size limit of 100 MB
To https://github.com/skorasaurus/tilemill-examples.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/skorasaurus/tilemill-examples.git'
As of June, github no longer allows files larger than 100mb. (Also see: https://help.github.com/articles/what-is-my-disk-quota)
To fix this, perhaps just throwing those files onto Amazon cloud S3 and making a .gitignore file to remove them and/or hardcode the url into the projects to trigger a download.