code review - How to codereview multiple git commits without using feature branches -
in team continiuous integration , therefore try avoid branches. instead commit/push master possible. means e.g. have committed 10 times , in between colleges have committed multiple times, including changes create conflicts when trying revert own commits.
this makes harder code reviews after having pushed commits because don't see way see sourcecode changes made through commits.
what ways, comfortable code reviews after having pushed commits?
in team continiuous integration , therefore try avoid branches. instead commit/push master possible.
that's bad approach, don't encourage continue working directly on master. branches meant used in such cases - many programmers working on same project.
depending on git hosting service you're using, suggest working on different branches , create pull-requests - there can make reviews want.
Comments
Post a Comment