I'm in the process of introducing feature-driven development to my team. We work with git and we're just starting to create topic branches for our work. From what I understand, a topic branch should be created for every feature or bug and the branches are supposed to be "short-living".
Our workflow involves creating an issue for each bug we discover (as well as features we want to introduce, but that aside for now) and then follow up by creating a branch for it that derives from master, make some changes, commit & push and then merge through pull request after code reviews.
So far this works well, however we've had a couple cases where bug fixes were a few lines of code (like 2-3). I instructed the developers to create a branch, but this seems like overkill - i.e - creating a branch for just a couple lines of code and a single commit...
What would be best to do in such cases? Would it be better to just work on the master branch for little changes rather than creating a branch for them?