Whether a branch should do one thing or a collection of things, for me, depends on how big/complex is the thing. If I’m making a very small change, e.g., a fix

Whether a branch should do one thing or a collection of things, for me, depends on how big/complex is the thing. If I’m making a very small change, e.g., a fix, I’ll work on master directly (personal work only! Shared work always uses the way we’ve agreed to work!). A slightly more complex change or an exploration or experimental change will get its own branch. A very complex change will have a base branch and feature branches off that base, possibly with issues, one per feature, merged into the base branch, which will eventually be rebased on then merged into master.