Gitflow is also solution to problem few teams actually have.
It is made to have few long term release versions, say you're making a database and need to support customer being major version or two behind for some years.
But if you are just making app for a client you really need just "this is released as stable and running in prod" and some flavours of dev/test environment and that doesn't need much of model to work at all, just prod/test branch with features never landing directly on prod is good enough.
It is made to have few long term release versions, say you're making a database and need to support customer being major version or two behind for some years.
But if you are just making app for a client you really need just "this is released as stable and running in prod" and some flavours of dev/test environment and that doesn't need much of model to work at all, just prod/test branch with features never landing directly on prod is good enough.