There is nothing more frustrating that firing off a 'git push' only to have it fail 3% from the end after 20 minutes. Split up large commits and push one at a timeĮven if it does work a single giant commit is fairly unwieldy.
GIT LARGE FILE STORAGE INSTALL
To rebase you need a parent and so you can't rebase the original commit.Īt this point, don't forget to install GitLFS.
gitignore, and your lfs tracking (see below).The reason for this is simple, if you end up needing to rebase in future and everything is in the initial commit, you will soon discover you are stuck. So here are some basic things we do when first pushing a project to GitHub. As you know GitHub has a file size limit of 100MB, but you often encounter problems well before you get to files of that size. However for me none of these work reliably in all cases. I've seen various posts on the net about using SSH over HTTPS and setting the HTTP post buffer parameter to a large value: git config http.postBuffer 524288000 However with large projects it is can be fairly common to see the dreaded: "fatal: The remote end hung up unexpectedly" The first thing we do is put the project under source control and we've always used GitHub and GitLFS which have worked well.
Recently we have started a few projects which were complete PC games with a large footprint.
So, to kick things off - let's start at the beginning with some source control. This is the first of hopefully many technical posts, we'll be talking about Unity, game dev and hopefully some retro game dev very soon.
0 kommentar(er)
