Using Talend with Git and Multiple Developers — Is There a Proper Workflow?

[dgp_itsum]

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 dev branch, but we're running into serious problems — each merge seems to affect over 100 files, and it's becoming unmanageable.

Is there an established or recommended way to use Git (or GitHub) effectively with Talend in a multi-developer environment?
Are we missing something fundamental here — or is Talend just not designed to handle this kind of workflow well?

Any guides, best practices, or real-world tips would be greatly appreciated.

[AxiomGRP]

┌────────────────────────────────────────┐
│ CLONE FROM REMOTE │
└────────────────────────────────────────┘
│
▼
┌──────────────────────────────┐
│ CREATE FEATURE BRANCH │
│ git checkout -b feature/x │
└──────────────────────────────┘
│
▼
┌──────────────────────────────┐
│ OPEN TALEND STUDIO │
│ AND DO YOUR WORK │
└──────────────────────────────┘
│
▼
┌──────────────────────────────┐
│ COMMIT CHANGES │
│ (Use Talend Git interface) │
└──────────────────────────────┘
│
▼
┌──────────────────────────────┐
│ REBASE DEVELOP │
│ git checkout develop │
│ git pull │
│ git checkout feature/x │
│ git rebase develop │
└──────────────────────────────┘
│
▼
┌──────────────────────────────┐
│ PUSH TO ORIGIN │
│ git push origin feature/x │
└──────────────────────────────┘
│
▼
┌──────────────────────────────┐
│ OPEN A PULL REQUEST │
│ Target: develop │
└──────────────────────────────┘
│
▼
┌──────────────────────────────┐
│ CODE REVIEW + MERGE │
└──────────────────────────────┘
│
▼
┌──────────────────────────────┐
│ DELETE FEATURE BRANCH │
└──────────────────────────────┘