We have a Matillion project with many jobs (Orchestration and Transformation). We have a "sprint" and deploy a new build every two weeks. We have a growing team of ETL developers using Matillion -- great news!
Except sometimes, Alice and Bob are both working on one job. For different purposes or "user stories." And let's say that this week, Alice is working on JobX, and she knows her work will not be completed by the end of the current sprint. But Bob needs to make some other, quick changes to JobX that will be completed for the current sprint, and deployed. How can they both work on JobX this week? Alice cannot make "unfinished, untested" changes because it needs to be deployed this week. She could make a copy of that job to work in, but the changes that Bob makes will not be reflected in her working copy. Tricky.
I wish Matillion had a "check in, check out" system for each job. Or something.
Unfortunately, your troubles are not new to the community. The scenario and issue you mentioned is currently a sore spot and not resolvable in Matillion's current Git implementation. I don't have any details but I know Matillion is aware of these types of issues and has some thoughts and work starting to help resolve these type of issues. The biggest hurdle as of right now is the lack of being able to do a true Diff between one version of a job/orchestration and another. If Diffs were possible then you could have 2 devs working the same job at the same time and when the first person checks in/pushes their changes it would go through fine. When the second dev goes to push it should notice that the local repo they are working off is out of sync and required a fetch first. Upon dev 2 fetching their should be an indication that there is a diff between dev 2's job and the one being fetched. Dev 2 would then theoretically be given options on how to resolve the diffs. This is the traditional source control process. The fact that the Diff part doesn't exist is what makes it impossible currently. I know it's being looked at and/or worked on right now but I wouldn't be able to give a status or ETA since I am a customer just like you.
I am also anxiously awaiting the ability to handle the same situation as you. I know this doesn't help right now but I hope it gives you some sort of comfort knowing that Matillion knows of the issue(s) around the Git implementation and plans to make it better.