![]() Any lower value should work as long as your push size is not larger than the set value. Some prior answers say to set it to 524288000 (500 MiB), but this number seems arbitrary and without merit. ![]() We don’t allow pushes over 2GB Why not set lower? This specific value is used because at least as of the year 2018, this value was documented (archive link) as the push size limit of GitHub: This can require dividing a large commit into smaller commits and pushes. In fact I would keep the commit push size under 1.8 GiB to be safe. It is however possible that you will need up to this amount of free memory to be able to use this value.Įnsure that each push to GitHub has commits that don't add more than this size of changes. 1 answer 0 votes P Mergey edited Did you try to log out and then log back into your GitHub account I know it sounds weird, but I had a somewhat similar problem (requesting authentication when I wanted to push changes) and that's what I did after seeing that GitHub recommended this kind of little handling. i/o timeout error: failed to push some refs to. Sourcetree: Invalid password for Github despite having a valid OAUTH token on Windows. In both cases, the number above is equivalent to 2 GiB. To stop push failure, LFS support can be disabled in the Project settings, which also disables GitLab LFS. If cloning a repo instead using git clone, it can be cloned with the same option: git clone -c http.postBuffer=2147483648 /path/to/myrepo If using GitHub, in the repo's directory, run this command to set http.postBuffer to what appears to be its maximum allowable value for GitHub: git config http.postBuffer 2147483648 Please think of us when you design your systems, tools, and applications. These kinds of issues are a constant problem for rural populations. I'm sure there is some configuration setting somewhere that makes git-or ssh or curl or whatever times out first-more tolerant of such networks, but I don't know what it is. I'm also lucky that I have this option available to me. Note that I can only do this itermittently because my cell connectivity is also intermittent. I switched networks-I moved to a slower, but lower latency cell network (my phone used as a hotspot)-and the problem disappeared. Note: The problem only exists in certain scenarios, but I have not determined what the pattern is. Issue: 'PUSH Failed refs/head/ - pre-receive hook declined' I've faced the problem of unable to push my changes to my origin branch and anything to master branch of a particular project repository as the size of that repo was over hard limit of 2GB. The speed of the network is fine, but the latency can be high. I found that this error pops up occasionally on high-latency networks (I have to use a Satellite dish for internet access for example). This is not an answer per se but more of an observation that may help others.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |