10
Noren
5y

An amazing git story: A month ago coworkers did research and started with merge requests. Their workflow is as follows: A Feature is developed in a branch, then a merge request is opened. After a very short review it will be closed (rejected) and merged without request. (wtf!) After that the develop branch will be tested later, in case of bugs, a new branch per feature is opened.

Comments
  • 1
    ... That seems very counter productive but I guess its a case of "that's how we do things around here" or "we don't have enough time to learn it properly".
  • 0
    Error: brain.exe is not running.
  • 1
    We have a similar workflow here 😐
    Creating a merge request and accepting it yourself within 2 Minutes
Add Comment