GitHub Connector for Language Ops

Overview

The Language Ops GitHub connector brings localisation into the development workflow. Instead of copying strings, Markdown, JSON, YAML, and docs between tools by hand, teams can route repository content into Language Ops for translation, QA, LQA, terminology checks, and review.

It is built for product teams, documentation teams, developer tooling teams, and agencies working with engineering-led clients.

Why Use This Connector?

GitHub is where product content changes. Language Ops adds the localisation workflow around it:

• Repository-aware translation workflows for strings, docs, config, and release content
• Pull request based delivery so engineering teams can review changes normally
• Terminology and style checks before translations land
• QA and LQA for software strings and documentation
• Automation hooks for release branches, docs updates, and recurring localisation jobs

Integration Methods

Pull request workflow

The standard developer-friendly approach:

1. Select repositories, branches, paths, and file patterns
2. Pull localisable content into Language Ops
3. Translate, review, and run QA/LQA
4. Open a pull request with the translated files

Engineering keeps normal code review and merge control.

Branch and release workflows

For release-driven teams:

• Trigger localisation from release branches
• Keep translations aligned with product versions
• Track changed strings between releases
• Push completed translations back before release cut-off

Documentation workflows

For docs and developer education:

• Markdown and MDX documentation
• YAML front matter
• API docs and changelog content
• Developer guides and support articles

Use Cases

Software string localisation

Route JSON, YAML, PO, properties files, resource files, and other string formats through a controlled translation workflow.

Documentation localisation

Translate docs without breaking Markdown structure, code samples, links, metadata, or front matter.

Continuous localisation

Use repository events to find changed content and keep localisation moving alongside development instead of after release.

QA before merge

Run terminology, placeholders, tags, formatting, and cross-lingual LQA checks before translated files are merged.

Technical Integration

Common integration paths include:

• GitHub App or token-based repository access
• Branch/path/file-pattern configuration
• Pull request delivery
• Webhook-triggered workflows
• XLIFF, JSON, YAML, Markdown, PO, and resource-file handling

We scope the exact route around your repositories, branching strategy, security requirements, and release process.

Pricing

Connector usage is included with your Language Ops subscription. Translation, AI, QA/LQA, and automation usage follow your plan allowances and metered token usage.

View pricing | Book a demo

Beta status

This connector is currently in beta. We are validating real-world GitHub workflows with early users before treating it as a fully supported production connector. If you want to use it, book a demo and we will confirm the right integration path for your setup.