Skip to main content

How to configure automatic Pull and Push settings for Git integrations

Setting up automated Pull and Push synchronization allows LingoHub to seamlessly import new source content from your Git repository and export translated files back to your codebase without manual intervention.

To access these settings, navigate to Projects and select your project. Then go to Settings and choose the Integration (GitHub/GitLab/Bitbucket/Azure) tab.

Automatic pull options

The Automatic pull setting determines how LingoHub imports updated source files from your repository:

  • Automatically on commits (Webhooks): Uses Webhooks to immediately trigger a pull whenever a developer pushes commits to a tracked repository branch.

  • Periodically: Automatically pulls updates on a set recurring schedule. You can configure the frequency to Daily or Weekly and specify the exact execution time (e.g., Weekly on Monday at 22:00).

  • None: Disables automatic pulls, requiring team members to trigger file pulls manually.

Automatic push options

The Automatic push setting determines how translated files are exported back to your Git repository.

  • Periodically: Exports translated files on a recurring schedule. Click Configure to choose between Daily or Weekly cycles and select your target time (e.g., Weekly on Monday at 22:00).

  • None: Disables automatic pushes, requiring manual export triggers.

Configuring push types: Pull requests (PR) vs. Direct push

Under Default push type, choose how LingoHub submits translated code to your repository:

1. Pull request (Recommended for review & protected branches)

Selecting Pull request enforces a peer-review workflow (four-eyes principle). LingoHub automatically creates a dedicated update branch in Git, pushes the translated files to it, and opens a Pull request.

  • Protected branches: Repository branches with branch protection rules enabled (e.g., requiring mandatory approvals or status checks) cannot accept direct pushes. Using the Pull request workflow ensures translations are properly vetted by developers before merging into production.

  • Pull request settings: Click Configure under Pull request settings to customize default PR branch naming patterns (e.g., lingohub_language_update_{base_branch}_{date}), PR titles, and detailed descriptions.


2. Direct push

Selecting Direct push commits localized files directly into the active target repository branch without generating a Pull request.

  • Direct push settings: Click Configure under Direct push settings to customize the default Git Commit message (e.g., Language update from LingoHub ☕) and Commit description.

Available placeholders for PR and Commit messages

When configuring Pull request settings or Direct push settings, you can use dynamic placeholders inside text fields (such as branch names, titles, commit messages, and descriptions). The following placeholders are supported:

Placeholder

Variable name

Output description

{date}

DATE

Current date at export

{datetime}

DATETIME

Current date and time at export

{user}

USER

Name of the user or trigger event

{project}

PROJECT

Name of your LingoHub project

{project_link}

PROJECT_LINK

Direct URL to the LingoHub project

{base_branch}

BASE_BRANCH

Name of the base repository branch

Need more help?

Couldn't find what you were looking for? Reach out to our team at [email protected], and we will gladly assist you.

Did this answer your question?