Though one thing that gave me some trouble .. You need to know how to do forks and update them via the command line to make a fork that you can keep up to date and upload your pull request ( something that gave me trouble)

@NoBlackThunder Makes sense. We use git (albeit using GitLab and GOGS rather than github) pretty extensively in my office, so I should be able to get up to speed (in theory - I'm sure I'll be eating those words if/when I get further into things). I'm thinking it would be something like setting the fork's upstream to point to the main upstream and making sure to pull with rebase into your local fork to stay up to sync? That's similar to how we manage feature branches while someone is making merges into our master branch. How many devs at large are working on things?

@NoBlackThunder Hey that's not a bad size at all (I'm the lead of a team of 3 including me, so I understand). At least the git history should be pretty clean! Thanks again for the info - much appreciated!