Chaser324’s gists · GitHub
Skip to content Sign in Sign up You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Instantly share code, notes, and snippets. Chase Pettit Chaser324 85 followers · 0 following http://chasepettit.com View GitHub Profile Recently created Least recently created Recently updated Least recently updated 1 file 1 fork 0 comments 0 stars Chaser324 / settings.json Created January 9, 2018 17:57 VS Code - Default Unity Settings { "files.exclude" : { "**/.DS_Store" : true , "**/.git" : true , "**/.gitignore" : true , "**/.gitmodules" : true , "**/*.booproj" : true , "**/*.pidb" : true , "**/*.suo" : true , 1 file 1 fork 0 comments 3 stars Chaser324 / ThreadedJob.cs Created April 8, 2016 15:43 Unity ThreadedJob class for doing work on a separate thread and checking status or waiting on the main Unity thread. // Source: http://answers.unity3d.com/questions/357033/unity3d-and-c-coroutines-vs-threading.html // // ***************************************************************************** // Example Job - Inheret from this class and override ThreadFunction: // ***************************************************************************** // public class Job : ThreadedJob // { // public Vector3[] InData; // arbitary job data // public Vector3[] OutData; // arbitary job data // 1 file 780 forks 132 comments 2884 stars Chaser324 / GitHub-Forking.md Last active November 18, 2026 12:06 GitHub Standard Fork & Pull Request Workflow Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential.
Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on. In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Creating a Fork Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j You can’t perform that action at this time.