managing heron / KUMC customizations

[dckc]

@nihr43 on heron_prod vs master... there is a certain risk in going away from the git master convention. I did change the default branch in this github repo. My thought was that master is for things that we expect to upstream and heron_prod is for our own customization. But maybe that's more trouble than it's worth?

ref #3 (comment)

[nihr43]

If I were working on anything that I expected to upstream, I would just add a [remote "upstream"] to .git/config

[dckc]

I don't understand how that's relevant to how we manage this repo. I guess I should drop by to talk some time.