One should know at all times on which branch is working on.
And to start with, on an organization a developer should not be able to push into master, it should be a protected branch.
That's why merge/pull requests are for.
Having master locally does not cost space or any thing.
But yeah you can update and resolve conflicts with origin/master, but it gets handy to have master locally for app check once in a while.
I do commit to master in some cases where there's only one branch (ex. project too small)
One should know at all times on which branch is working on.
And to start with, on an organization a developer should not be able to push into master, it should be a protected branch.
That's why merge/pull requests are for.
Having master locally does not cost space or any thing.
But yeah you can update and resolve conflicts with origin/master, but it gets handy to have master locally for app check once in a while.
I do commit to master in some cases where there's only one branch (ex. project too small)
What is the benefit for "app check"