So I just completed a short but very useful class to learn about git and GitHub, covering the typical commands and workflow. I’m curious to know how Hugo does the git workflow, like branches, merging, rebasing, work-in-progress stuff and squashing commits when it’s done…
I took a peek at the branches and if I had to guess, it seems to me the main work happens on everyone’s forks and pull requests are submitted. When they are accepted and merged, it goes into the master branch. Then when it’s time for a new version, a new branch is made from the master at that point with the version number name. Then it’s… merged? as the new stable branch and a release is built on that? And all the version branches are kept for posterity (presumably so one could go back and build hugo as that past version? or… is it just to keep a history?)
I thought there was a way to view a repository tree, like in GitX, just from the GitHub website but I guess there isn’t, I’d have to install a git gui program on windows to do it.
I would think a typical workflow would be to branch off the master when you are starting a new version, and then merge that back into master when you are read, but that doesn’t exactly seem to be the model here.
Thanks for any insight!