When looking at Git as a potential VCS repository for development in Denodo, how exactly do we handle branching, e.g. when implementing the [Gitflow Workflow](http://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow)?
This requires several branches of which some can be mapped to an environment (e.g. *develop* branch to the development server and *master* to the production server). This poses no problem as you can define a custom branch in the Denodo server's VCS configuration.
However, when using the *feature* or the *release* branches, you'll have branches which exist for a period of time, until they are merged back into the another branch (e.g. *develop* or *master*).
I'm aware that you can define a different branch for a single database, but when you have several developers working in a shared environment with serveral databases (with inter-database dependencies), this is not ideal (unless you have a full-fledged environment for each developer individually, as described [here](https://community.denodo.com/docs/html/browse/6.0/vdp/administration/version_control_systems_integration/scenarios_and_recommended_uses/scenarios_and_recommended_uses#developers-use-their-own-virtual-dataport-server)).
The issue is when switching branches (either for the whole repository or a single database), Denodo will show the warning *This database will no longer be synchronized to a VCS repository*. How do we deal with that? After confirming the warning and issueing a *pull*, Denodo will still show an orange indicator.
