We have a small team of developers working on Matillion and started using the GIT integration to track changes then push to Azure DevOps Repos which works well.
With some other projects, we automate a push to the remote repository on a daily or weekly basis (just before the weekend) using command line GIT tools and wondering if it's possible to do this with Matillion?
I appreciate the FAQ's documentation suggests "Matillion does not recommend manually using Git tools to amend your repository from outside Matillion" so I'm wondering if anyone has any other solutions?
Unfortunately, there isn't a great answer as of this moment but the Git implementation has been a subject being talked about as of late. If you look at the anatomy of Matillion's Git integration, they are simply riding on exporting each orchestration or transformation to a JSON file, put into a structure, which is then eventually pushed to a remote repo. The JSON generated for individual orchestrations and transformations from Matillion's Git integration is identical to doing a normal orchestration export from the UI. In my opinion you could employ a process where you export a project either to 1 file or broken into a file per orchestration and diff those files to the previous or what is currently in the remote repo. If there are no diffs then push the changes and your done. Of course there are many other scenarios to take into account but in theory that would work. If you ever needed to bring an orchestration back from the remote repo you simply fetch it and import it back in to the project. We do this part all the time for deployment purposes.
The only reason Matillion tells you not to use other methods is because the structure of that repo has to be 100% correct from a structure and file perspective in order for the built in Git integration to function correctly. If you don't plan on using the built in Git functionality then you can come up with your own process.