GitLab Sync

GitLab Sync pushes your repository to GitLab on every push. It handles the full checkout, validation, and push — including full git history and optional Git LFS objects.

Features:

• Full history sync (fetch-depth: 0)
• Optional Git LFS support
• Optional force push
• Clear error messages for misconfigured secrets

In your GitHub repository go to Settings > Secrets and variables > Actions and add:

Tip: Generate a GitLab PAT at User Settings > Access Tokens. Minimum required scope is write_repository.

Create .github/workflows/sync-to-gitlab.yml in your repository:

name: Sync to GitLab
on:
 push:
 branches: [main]
jobs:
 sync:
 runs-on: ubuntu-latest
 steps:
 - name: Sync to GitLab
 uses: kujov/gitlab-sync@main
 with:
 gitlab_url: ${{ secrets.GITLAB_URL }}
 username: ${{ secrets.USERNAME }}
 gitlab_pat: ${{ secrets.GITLAB_PAT }}

That's it, every push to main will mirror to your GitLab repository.

Change the trigger to sync on pushes to any branch:

on:
 push

Use with caution — this overwrites the GitLab repository history:

 - uses: kujov/gitlab-sync@main
 with:
 gitlab_url: ${{ secrets.GITLAB_URL }}
 username: ${{ secrets.USERNAME }}
 gitlab_pat: ${{ secrets.GITLAB_PAT }}
 force_push: true

To also sync LFS objects, enable git_lfs. Make sure LFS is enabled on your GitLab repository before using this.

 - uses: kujov/gitlab-sync@main
 with:
 gitlab_url: ${{ secrets.GITLAB_URL }}
 username: ${{ secrets.USERNAME }}
 gitlab_pat: ${{ secrets.GITLAB_PAT }}
 git_lfs: true

Authentication failed Verify GITLAB_PAT is valid and has write_repository scope. Tokens expire — check User Settings > Access Tokens on GitLab.

Push rejected (non-fast-forward) The GitLab repository has commits not in GitHub. Use force_push: true to overwrite, or manually reconcile histories.

LFS objects not syncing Ensure Git LFS is enabled on the GitLab repository (Settings > General > Visibility > Git LFS) and that git_lfs: true is set.

Invalid gitlab_url format The URL must be a full HTTPS URL ending in .git, e.g. https://gitlab.com/user/repo.git.

Issues and pull requests are welcome. If this action is useful to you, consider starring the repository.