These Git. feature branches look pretty generic, how do we know when there’s a conflict if we’re working exclusively out of Copado?
These Git. feature branches look pretty generic, how do we know when there’s a conflict if we’re working exclusively out of Copado?
The explanation behind why Copado creates "generic" feature branches.
Written by Dustin Levi
Updated over a week ago
Committing to a Git feature branch, not only adds an extra layer of protection by NOT immediately committing to the actual branch. It also allows you to create those pull request & merge conflicts before you move to the next sandbox. So with Copado, the manager/admin is always able to see & correct any conflicts.
