Open danisev7 opened 2 years ago
Ok, so a new branch for each specific feature sounds good.
But we need to encourage people to review/approve the changes first. Otherwise it'll sit there forever or just end up being merged without review
The only problem I can forecast with this approach is that some conflict resolution knowledge on Git is required. Aside from it, it is the best way to work in parallel.
To make the pull requests for this project, I propose to do a lightweight feature branches.
It will be the same feature branches strategy proposed at Gitflow Workflow but without the use of development branch because this is a very small project.
Basically the workflow will be:
To find a peace of code to improve To open a new branch with the name feature-xxxxx To do a pull request for this branch