Closed LuHKae closed 4 years ago
this makes perfect sense for me, I used the branch naming convention feature/ and hotfix/ already but we should agree on a full flow.
👍 Very good idea. Since I was working alone on this project I did not think about something like this. But it seems like you guys are motivated to push this project further 😃 So it definitely makes sense to define a workflow. I like the idea of gitflow. This sounds promising. But we should add some development/contribution infos to the readme, if others want to contribute as well...
Ok so I created the develop branch (again 😃). I think we should agree on the default settings go gitflow. So we use git flow init -d
to initialise gitflow.
I think we can close this issue, right?
I would suggest to use a GIT workflow like gitflow.
My suggestion ist gitflow:
Here is on graphical overview of the flow between the branches: https://danielkummer.github.io/git-flow-cheatsheet/