💬 Users previously had no straightforward way to export screenshots linked to project strings for documentation, reporting, or QA in a format suitable for offline, editable review. Screens were only accessible in the dashboard, or exportable in Markdown or PDF.
⭐ With this update, target screenshots can now be exported directly in Excel format, in bilingual mode, making it easy to share them across teams without requiring dashboard access.
⚙️ The API now enforces stricter validation for tag categories. Tags can only be assigned to categories that already exist in the project. If a non-existing category is specified, the API will return an error instead of silently assigning the tag to “None.” This prevents errors caused by typos or misconfigured scripts and ensures data consistency.
⚙️ Connecting Figma to the right project is now much faster. Previously, users with a large number of projects had to scroll through a list to find the correct one. With this update, the Figma plugin includes a search bar on the project selection screen, allowing users to quickly filter and select the right project by name. This streamlines setup and saves time when connecting designs to GL Strings.
⚙️ GitHub repositories can have a wide range of access management settings and permissions, which sometimes makes integration setup unclear. With this update, GL Strings now handles these scenarios more gracefully. During configuration, the system validates token scopes, repository admin rights, and workflow permissions, and highlights what may be blocking the setup. Users receive clear guidance with direct links to the relevant GitHub settings, making it easier to adjust permissions and complete the configuration smoothly. Existing configurations remain intact even if tokens expire or permissions change.
⚙️ With this improvement, file configurations in the GitHub integration are now far more flexible. Previously, users were limited to simple settings like file format selection and adding tags per file. Any advanced file options required manual editing of JSON configs in the repository. Now, all mandatory and optional file options can be configured directly in the GL Strings UI. The system automatically detects file formats by extension and pre-fills required fields. It shows only the relevant options for each format — for example, column mapping for Excel, CSV, or TSV files. Optional parameters can be added, removed, or reset at any time, with instant validation and clear error messages to guide users.
The target files inherit properties from their source files' configuration where applicable, ensuring consistency across workflows, while still allowing format-specific optional configurations to be applied where needed. Collapsible option panels, filtering, and search make navigation manageable even for large repositories with many files. Together, these enhancements eliminate the need for manual JSON editing, reduce integration errors, and give teams full control over complex, multi-format file configurations directly from the GitHub Integration page.
⚙️ If Excel, TSV, or CSV files are part of a project’s scope and users want to push existing translations to GL Strings through the integration interface, additional configuration is normally required to correctly map language columns. With this update, the GitHub integration now validates that this configuration is present and automatically adds it when needed. This ensures that spreadsheet files are mapped properly by default, so translated files can be pushed seamlessly without extra setup.
⚙️ Managing GitHub integrations is now easier. Previously, users had to navigate through integration settings to find and edit their GitHub configuration. With this update, a GitHub Integration button appears directly on the project dashboard whenever an integration is configured. Authorized roles can use it to open the GitHub onboarding page with the configuration pre-filled and ready to edit. The integration page also includes a branch dropdown, ensuring users always manage the correct branch configuration.
⚙️ Pushing translations to GitHub is now more flexible. Previously, every pull request included all configured files, requiring users to review all translation changes across all configured files in one pull request, even if they only wanted a subset of files. With this update, users can select one or multiple files from their integration setup and create a targeted PR containing only those translations. Each PR requires a title and commit message, and the UI ensures only valid files can be selected. Clear feedback is provided throughout the process, with GitHub errors displayed directly in the UI and retry options available if something goes wrong. This makes collaboration cleaner, reduces review noise, and gives teams granular control over which translations are pushed for specific features, components, or releases.
⚙️ Teams working with multiple branches in GitHub now have the flexibility to choose where translations should go. Previously, pull requests could only target the single branch configured during setup, which limited workflows for feature, release, or hotfix branches. With this update, users can select a different GitHub branch from a dropdown when creating a manual PR, ensuring translations are pushed to the right place. The default remains the branch defined during integration, but users can temporarily switch branches per PR without altering the overall setup. If branches cannot be retrieved from GitHub, the UI provides clear error states with retry options.
⚙️ Until now, users had to leave GL Strings and check the logs in GitHub directly, which made debugging cumbersome. With this new feature, workflow history and logs are centralized inside the GitHub Integration page on GL Strings. Users can view recent push or pull runs, check their status, inspect detailed logs, and jump directly to GitHub when needed. This saves time, reduces context switching, and makes troubleshooting translation workflows easier.
🛠 In dark mode, GitHub integration details such as the URLs and source/target file paths were not visible in the edit screen. This has been fixed for better readability.
🛠 The Export button in the changelog modal was invisible in dark mode. The button color has been corrected.
🛠 For keys with very long names, the key name overlapped with the Export button in the changelog modal. The button now remains properly aligned and long names truncate with ellipsis or wrap cleanly.
Learn about our latest features and improvements
Read the Full Article
Learn about our latest features and improvements
Read the Full Article