I recently started working with GitFlow model as implemented by bitbucket. And there is one thing that is not completely clear to me. We try to regularly address our technical debt by backlogging, planning, and implementing the refactoring tasks. Such refactoring branches end with pull-requests that are merged in develop. My question is where do the refactoring branches belong in GitFlow? Using feature prefix seems the most logical, however it does not feel entirely right, because refactoring does not add any new functionality.However using bugfix prefix seems not right as well as there is no actual bug refactoring fixes.Creating a custom prefix on the other hand seems like complicating if not over-engineering the things.Did you have such situation? Which practice do you use to address this? Please explain why.
Where does refactoring belong in GitFlow branch naming model?
git;refactoring;branching;gitflow
Refactoring work should go in a feature branch.The prefix feature is just a word to describe a discrete programming task, you could choose any word you like, any branch from development is either a feature branch or a release branchAdding a new prefix such as refactoring is problematic. As you will often do some refactoring when adding a feature, you are simply giving yourself a naming problem and adding confusion. ie. some of our feature branches are called 'refactoring', no they don't contain all the refactoring work and sometimes they have bug fixes or features in them'similarly hotfix branches are not called hotfix because they contain hotfixes, but because they branch from master rather than develop 