Here are some better alternative names for the "master" branch in your source
code repository:
- bleeding-edge
- nevergreen
- works-on-my-machine
- happy-merging-XD
- there-be-real-users
- features-come-here-to-die
- (L°O°)L*|*|_
4 replies
Replying to @coderbyheart
"mainstream" also sounds right to might ...
Replying to @coderbyheart
No seriously: there are teams discarding the use of the master/slave
terminology. And if you think about it, master is the wrong word for the branch
of the source-code repo which, for the most projects I have worked in, contains
the latest source code.
Replying to @coderbyheart
"master" has the meaning of being a owner and controller over others. But if you
are using feature branches, the control is actually inverted, and master is
"controlled" by the feature branches.
Replying to @coderbyheart
So next time you start a new repo, maybe name your main branch not master, but
saga, because sagas are "a long story about history", and this is what the main
branch of your repository actually is.