GitHub and XTRF Integration

Kenneth Larmer 1 year ago in API updated by Bartosz Budzyński 1 year ago 3


Has anyone integrating XTRF with GitHub?

We have a client inquiring about the integration and I’m wondering if anyone has had any success with this?

Thanks in advance,


Hey Kenneth,

What kind of integration are you thinking about - can you please share some use cases? One- or two-way? 

I believe the main goal here would be to have file versioning and I'm not sure GitHub is the best tool for this particular case, as it might be tricky to work with decentralized repositories. Have you considered using, for example, Google Drive or Dropbox? That would be a lot easier to develop and way more friendly to use. 

Hi Bartosz,

Thank you for your reply.

The client in queston uses GitHub to house their XML files. Their current approach to localization is that they have to download the XML files from GitHub, upload to our CP, we translate and deliver through the CP, client downlads files and commits to GitHub. They expressed an interest in exploring the possibility of integrating this (posting the files for translation from GitHub to our XTRF instance and then our XTRF instance pushing the files back to GitHub).

Our CAT tool has an integration available, but my concern with this approach is that we are by-passing XTRF. My prefered approach would be integrate via XTRF and use XTRF to pass the files to the CAT tool. 

We are starting to see more an more inquiries in relation to GitHub.



Hi Kenneth,

Thanks for clarifying the workflow.

It is possible to implement such integration using Client Portal API and Git client, however there're still some more things to figure out, for example dealing with conflicts or even there's a need to take a one step back and consider if pushing should really be the "pushing" in Git terms or just a pull request for particular repo. Is there only one repository per project or one for all projects? 

Nevertheless, such integration is doable but as far as I'm concerned was not yet developed by any of our Clients nor by internal XTRF teams.