-_-
How do folks feel about `prerelease` as a default branch name for open source projects
-
-
- 11 more replies
New conversation -
-
-
I prefer main because it needs no description. If you tried to describe what a master branch was to someone who just learned branches, you’d probably say “it’s the main branch.” It works for OSS project, apps, whatever.
-
Also, I think it’s the most likely to become conventional.
- 1 more reply
New conversation -
-
-
I feel it presumes a certain branch/merge policy.. some use that one for release. It's of course the ultimate NIH bike-shed, but 'trunk' is well established already in other VCS and suits?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We ship our main branch on my main project at work as continuous delivery - there’s no concept of cutting a release. The merge is the release. This name would feel weird there. I like `main`.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Make master branches the 'kitchen' because that's where you cook up and serve releases from. Branch the kitchen Keep that busted pull out of my kitchen
-
git checkout -b basement/jason
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.