AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Github desktop wont push to fork2/20/2024 There are two important settings that your Unity project needs to have before you use it with git: Step 2 - Project settings for version control It’s best to avoid spaces and special characters as Unity will create a directory from the project name.Select the path where your new project’s directory will be created.You download it, or alternatively a visual client, hereĪ free account is fine to get started with. We’ll be using the command line client in this tutorial. It is worth getting a recent version of Unity because they have better support for version control. You can download and install different versions of Unity using Unity Hub which is available here. To follow along with this guide you will need the following: In this how-to guide we show you how to set up a Unity project for version control using GitHub. Step 20 - Move quickly by avoiding mistakes.Step 15 - Cloning a clean copy from GitHub.Step 14 - Push your local changes to GitHub.Step 13 - Connect your local repository to GitHub.Step 12 - Setup SSH keys to access GitHub.Step 11 - Create a repository in GitHub.Commit hash, our commit’s unique identifier.Step 5 - What to commit? What to ignore?.Step 4 - Take a look inside your new project.Step 3 - Initialize the project for git.Step 2 - Project settings for version control.T06:57:08.753Z - info: Subscribed 'lvonk' to Alive channel T06:57:08.610Z - info: execPath: '/Applications/GitHub Desktop.app/Contents/Frameworks/GitHub Desktop Helper (Renderer).app/Contents/MacOS/GitHub Desktop Helper (Renderer)' T06:57:08.313Z - info: found account: lvonk (Lars Vonk) T06:57:08.311Z - info: loading 13 repositories from store T06:40:35.930Z - info: Action 'checkout branch from list' for 'xxx/yyy' took 0.149s T06:40:35.690Z - info: account found for repository: xxx - lvonk (has token) T06:40:22.492Z - info: : Refreshing sidebar indicators for 12 repositories took 3.8s of which 0.0s paused, total 3.8s T05:01:50.162Z - warn: Alive web socket request failed: TypeError: Failed to fetch T01:57:41.774Z - warn: Alive web socket request failed: TypeError: Failed to fetch This seems to have fixed my issue with pushing large numbers of files.īe nice if this setting could be configured through GitHub Desktop. Git config -global http.lowSpeedLimit 1000 After some searching on timeouts I did find a recommendation to add the following to your config: I do not have any large files, just lots of little ones. But quitting both and just opening GitHub Desktop still ended up with a stalled push. Initially I thought it was because I had opened the repository in VS Code while GitHub Desktop was still pushing files. Then it happened again, this time with GitHub Desktop hanging. Initially my problem went away and I was able to push without problems and even VS Code worked again. I then installed GitHub Desktop to see if that would fix the issue. Uninstalling and reinstalling didn't help. At first I thought it was VS Code just couldn't handle an initial push with a large number of files, and git on the command line had the same issue.
0 Comments
Read More
Leave a Reply. |