Using branches - rlsweeney/Sweeney_RA_Manual GitHub Wiki

Branches should be "issue" focused
When you got started, I told you to make a branch with your name and work off that. In general, if you just want to play around with some files, this is still a good place to work.
But going forward we should try to have one branch for each thrust of analysis. So, for example, if we are working to match the TWP data to the EIA data, that could be in a branch called "eia_matching".
The benefit of this is so we have clear pull requests. Also, this means that if you're also working on say predicting output, we don't necessarily want to merge those changes until they're ready, which may be after the eia_matching is ready.
More info on this "branch-commit-pull request" workflow here
One important thing to remember: With few exceptions, you always want to create your branch off the master branch. This facilitates merging later.