Term checks in code repositories

You can connect code repositories from GitHub, GitLab or Bitbucket to Lexeri and turn on automatic term checks to ensure that correct terminology is used in UI texts. And of course the corrections can also be inserted back into the development workflow using merge or pull requests, entirely without copy & paste.

Schedule a demo

What Lexeri term checks can do for software teams

Syncs texts from code repos

Lexeri connects to your code repositories, syncs only the selected documents and extracts, for example, your UI texts from them.

Runs automatic checks on strings

Lexeri runs automatic checks on the extracted strings. You will find the test results in Lexeri as well and can make corrections in an editor.

Creates pull or merge requests

Once you have corrected individual strings, you can send them back to the code repository in a merge or pull request.

Term checks in software development

How term checks from a code repository
work in Lexeri

1. Planning term checks

You can plan your automatic term checks once you have connected a repository to Lexeri. To do so, select the interval at which a test should run. The next step is to select the preferred termbase and a language for the term check.

2. View the results in Lexeri

Your active automatic term checks will be shown to you in the term checks. Here you see an overview of the terms found in the last check. You access the detailed results by clicking on the results button.

3. Editing strings in Lexeri

The term check results list all segments that contain the relevant term hit. Here you can edit the selected segment and, if necessary, run another term check for this segment.

4. Sending back changes

Once you or your colleagues have adapted the strings in Lexeri, you can send the changes back directly from Lexeri. Depending on the system, a pull or merge request is used for this in software development. Your colleagues can use this to track the changes, run automatic tests and make adjustments if necessary. Lexeri recognises automatically which documents have changed and need to be updated.

What you need

Here are the things you need for an automatic term check in Lexeri:

Access to a repository in one of the supported systems
The system must be reachable from outside
A personal access token with API access

We would be delighted to assist

Feel free to reach out if you need help or have any questions. We would be delighted to coordinate with your IT and help to set up your code repository.

Supported file formats:

Lexeri can read strings in the following file formats:

Yaml
JSON
Xliff
PO/GNU Gettext
Java Properties
INI files
SRT subtitle files
Android Resource XML
.Net RESX
Go-I18n

Lexeri’s plug-ins

Term checks in your systems

Perform your term checks where the texts are produced: You can run term checks directly in your systems with the Lexeri plug-ins.
Whether it’s the Office Suite in Microsoft Word and Excel, writing emails in Outlook or checking UI texts in Visual Studio Code or Figma: Lexeri offers integrations that are easy to use and that help you to maintain consistent terminology.

All plug-ins