https://community.qlik.com/t5/Talend-Studio/Using-Talend-with-Git-and-Multiple-Developers-Is-There-a-Proper/m-p/2513903#M147454 <P>┌────────────────────────────────────────┐<BR />│ CLONE FROM REMOTE │<BR />└────────────────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ CREATE FEATURE BRANCH │<BR />│ git checkout -b feature/x │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ OPEN TALEND STUDIO │<BR />│ AND DO YOUR WORK │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ COMMIT CHANGES │<BR />│ (Use Talend Git interface) │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ REBASE DEVELOP │<BR />│ git checkout develop │<BR />│ git pull │<BR />│ git checkout feature/x │<BR />│ git rebase develop │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ PUSH TO ORIGIN │<BR />│ git push origin feature/x │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ OPEN A PULL REQUEST │<BR />│ Target: develop │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ CODE REVIEW + MERGE │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ DELETE FEATURE BRANCH │<BR />└──────────────────────────────┘</P> Thu, 10 Apr 2025 17:16:41 GMT AxiomGRP 2025-04-10T17:16:41Z https://community.qlik.com/t5/Talend-Studio/Using-Talend-with-Git-and-Multiple-Developers-Is-There-a-Proper/m-p/2513791#M147450 <P>We're facing a major issue at our company when it comes to collaboration in Talend. Multiple developers need to merge their individual branches into the<SPAN>&nbsp;</SPAN><CODE>dev</CODE><SPAN>&nbsp;</SPAN>branch, but we're running into serious problems — each merge seems to affect over 100 files, and it's becoming unmanageable.</P> <P>Is there an established or recommended way to use Git (or GitHub) effectively with Talend in a multi-developer environment?<BR />Are we missing something fundamental here — or is Talend just not designed to handle this kind of workflow well?</P> <P>Any guides, best practices, or real-world tips would be greatly appreciated.</P> Thu, 10 Apr 2025 08:24:38 GMT https://community.qlik.com/t5/Talend-Studio/Using-Talend-with-Git-and-Multiple-Developers-Is-There-a-Proper/m-p/2513791#M147450 dgp_itsum 2025-04-10T08:24:38Z https://community.qlik.com/t5/Talend-Studio/Using-Talend-with-Git-and-Multiple-Developers-Is-There-a-Proper/m-p/2513903#M147454 <P>┌────────────────────────────────────────┐<BR />│ CLONE FROM REMOTE │<BR />└────────────────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ CREATE FEATURE BRANCH │<BR />│ git checkout -b feature/x │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ OPEN TALEND STUDIO │<BR />│ AND DO YOUR WORK │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ COMMIT CHANGES │<BR />│ (Use Talend Git interface) │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ REBASE DEVELOP │<BR />│ git checkout develop │<BR />│ git pull │<BR />│ git checkout feature/x │<BR />│ git rebase develop │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ PUSH TO ORIGIN │<BR />│ git push origin feature/x │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ OPEN A PULL REQUEST │<BR />│ Target: develop │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ CODE REVIEW + MERGE │<BR />└──────────────────────────────┘<BR />│<BR />▼<BR />┌──────────────────────────────┐<BR />│ DELETE FEATURE BRANCH │<BR />└──────────────────────────────┘</P> Thu, 10 Apr 2025 17:16:41 GMT https://community.qlik.com/t5/Talend-Studio/Using-Talend-with-Git-and-Multiple-Developers-Is-There-a-Proper/m-p/2513903#M147454 AxiomGRP 2025-04-10T17:16:41Z