Can't push commits to GitHub. Won't ignore large db file.

Hi,

If you select “Let me decide” for the database tracking settings, you can select specific tables or avoid ones that are too large. Then if it’s still being tracked or pushed you can delete the file and it won’t just reappear the next time you backup your database.

Also, do you have the full path to the file (wp-content/uploads/sites/2/revisr-backups/revisr_wp_posts.sql) in the “Files/Directories to ignore”?

This is just buggy as all get out.

Thanks for telling me about the “Let Me Decide” option. I chose the option to ignore all database tables, simply to get this plug-in to push one change to GitHub.

I put the full path the large file causing the error message to the ignore section in two ways, both with the preceding “/” forward slash and without.

Still got error messages about the large file when I tried to push commits.

Then I tried just deleting the offending file from the server. Still getting an error message about the offending file being too big. Really? It’s not even on the server any more.

Then I tried to commit recent changes locally. Most of the recent changes are database tables. When I try various combinations of file to commit, I get the following error message on a white screen:

Warning: htmlspecialchars() expects parameter 1 to be string, array given in /home/visourcedev/public_html/wp-includes/formatting.php on line 3203

Warning: Cannot modify header information – headers already sent by (output started at /home/visourcedev/public_html/wp-includes/formatting.php:3203) in /home/visourcedev/public_html/wp-includes/pluggable.php on line 1178

Hi,

Sorry to hear you were having issues. I just released version 1.9.5, which should fix a few of the problems you ran into, including the PHP warning messages you mentioned above.

I’m thinking what happened here is you deleted the backup file manually, then tried a push. Because the deletion hasn’t been committed, Git would still try to push that file.

Then when you tried making the commit, there was an error with that, causing the warnings you saw.

I’m marking this topic as resolved, but please feel free to open a new one if you run into any further issues. Thank you.

That make sense. I’ll install the update.

I actually was getting the PHP warning messages before I removed that file manually. All of the waiting commits were database files. When I tried to selective unstage some of the files and commit, I was getting similar PHP error messages.

The PHP messages have disappeared. Thanks. But I still can’t push any commits to Github. I committed a large batch locally. Then I deleted the big file and committed that deletion locally. Tried to push to remote and got the error message again about large file being too big for Github.

Not sure, but it looks like this may help you:
https://github.com/githubtraining/zzz_deprecated-feedback/issues/63

Since it’s in the repo history it’s still being pushed up, it may just be easier to remove the .git folder if your repo isn’t critical yet and start fresh with the appropriate tracking settings. Also I could not find any file size limits for Bitbucket, so you may have some luck with that as well.

Marking this as resolved again, there is nothing we can feasibly do plugin-side for this, at least until GitHub rolls out LFS.

Thanks! Sounds like it is resolved at this point. I really appreciate your plug-in and hope to use it on future projects.