Yes, from my past experience the master branch is the clean branch. Everything gets merged into that branch before it is pushed up to staging or production.
I only say "one should not work on master", if you are not team lead. I was never team lead. I was always one memeber out of 2-15 other people. So, unless I am working on personal projects, then of course, you can push stuff from master after you have merged your separate branch changes. Because no one else will do it for you.
Yes, from my past experience the master branch is the clean branch. Everything gets merged into that branch before it is pushed up to staging or production.
I only say "one should not work on master", if you are not team lead. I was never team lead. I was always one memeber out of 2-15 other people. So, unless I am working on personal projects, then of course, you can push stuff from master after you have merged your separate branch changes. Because no one else will do it for you.
I think this is where the confusion lies.
I totally agree with you James. I have a similar workflow when working in a team