Fork-and-pull or branching method of contributing?

Both are methods that allow collaborative coding but just different ways to go about it with their own positives/negatives. Positive of `fork-and-pull` (which is how the course is setup now) is that the main repo is more protected from accidental changes AND is how a lot of open science happens. Negative is that it can be more confusing because there are more copies of the repo floating around and folks have to make PRs starting from their fork.

Both have their merits but we should talk about which we want to teach. USGS is switching to branching, so if we end up sharing a training repo, we may need to have different options/versions.