If you're interested in integrating Smartling directly with your source repositories, there are a few options:
- A GitHub specific connector.
- A general repository connector for both Git and SVN repos.
- You can choose to build a custom integration, using our APIs, which have supporting tools and SDKs.
Here are the main differences between these options:
| GitHub Connector | Repository Connector | Custom API Solution | |
| GitHub hosted Git repos | Yes | Yes | Yes |
| Self hosted Git repos (GitHub Enterprise) | No | Yes | Yes |
|
GitLab or Bitbucket hosted Git Repos |
No | Yes | Yes |
|
Self hosted SVN repos |
No | Yes | Yes |
| Requires pull requests for changes to be detected by Smartling | Yes | No | No |
|
Single repository for source and translations |
Yes (GitHub connector will create a new translation branch.) | Yes (Repository connector will push translations only to the same repository and the same branch from where it found files with new strings for translation.) | Yes |
| Multiple repositories | Requires multiple Smartling projects | Yes (A single Smartling project can have files from multiple repositories. With custom configuration, multiple Smartling projects can have files from the same source repository.) | Yes |
| Configure by branch | Single | Multiple | Custom |
| Deliver translations by pull request | Yes | No | Yes |
| Operate behind firewall | N/A | Yes | Yes |
Ready to use the Smartling APIs? Click here.