Best Practices and tips for using Git with the Talend products.
Best practices for Git:
All developers should work on branches other than the 'master'.
For each development (bug, new features), a feature branch is created.
Remote Git projects open in local mode in Talend Studio. By default, when working on a remote project changes are automatically committed to Git.
When developers are connected to Talend Cloud, however, they can activate the manual Git commit mode and manage their changes in Talend Studio before committing them to Git and pushing them to the remote server.
For more information on how to work with branches, see the Talend Studio User Guide.
Each time developers reach a Milestone (for releases, features, sprints, etc.), a Tag should be used. A new Tag should be created when the feature is ready for delivery (Production environment). If the tagged version needs bug fixing, a branch can be created from the Tag and the fix can then be included in the 'trunk'/'master'.
It is recommended to define patches as minor versions and full releases as major versions.
When working in a specific branch, it is recommended to filter the project on this branch using the Git Branches allowlist option in order to reduce the use of disk resources and improve performances.