Example : Dev-A and Dev-B are working on Project-1. Dev-A works on BA branch and Dev-B works on BB branch of same project. Need to ensure changes are local to branch first. At the moment changes on BA is also seen on BB which is not desired.
If you want each developer to work in their own branch then each developer needs their own version. Each developer can then use their own version as their user workspace where they can create, commit and merge branches.
Thank you for the information.
- Is there a limitation on how many versions can be created for one project?
- Does one project one version always have to work with one environment?
- How do we revert changes without changing branch?
- When we want to update working branch with latest changes on Dev/Master fetch doesn't really help and we end up getting conflicts during merge. How can we best avoid this?
- Any better way to review the json when merge conflict occurs?
Anupama - do go through the below YouTube video. It gives a good overview on Git best practices in Matillion.
Git Integration - Recommended Workflow | Matillion ETL
Is there any best practice to follow to review the modified pipelines? Currently we use files modified from git repo to help users identify changes at some level but there is no good way to understand what exactly has changed