Skip to content

ci: add GitHub to GitLab auto-sync workflow#41

Closed
jarcherNV wants to merge 4 commits into
mainfrom
dev/jarcher/autosync
Closed

ci: add GitHub to GitLab auto-sync workflow#41
jarcherNV wants to merge 4 commits into
mainfrom
dev/jarcher/autosync

Conversation

@jarcherNV

Copy link
Copy Markdown
Collaborator

Add GitHub Actions workflow to automatically sync commits from GitHub main to GitLab via merge requests:

  • Cherry-picks commits from GitHub onto GitLab sync branches
  • Excludes .github/ directory (GitHub-specific CI files)
  • Creates/updates GitLab MRs for review before merging
  • Preserves commit authorship and dates
  • Triggers on PR updates (for testing) and main branch pushes

Requires GitHub secrets: GITLAB_TOKEN, GITLAB_HOST, GITLAB_PROJECT_PATH

Add trivial README marker to ensure sync changes are visible in GitLab MRs.

Add GitHub Actions workflow to automatically sync commits from GitHub main
to GitLab via merge requests:

- Cherry-picks commits from GitHub onto GitLab sync branches
- Excludes .github/ directory (GitHub-specific CI files)
- Creates/updates GitLab MRs for review before merging
- Preserves commit authorship and dates
- Triggers on PR updates (for testing) and main branch pushes

Requires GitHub secrets: GITLAB_TOKEN, GITLAB_HOST, GITLAB_PROJECT_PATH

Add trivial README marker to ensure sync changes are visible in GitLab MRs.
@copy-pr-bot

copy-pr-bot Bot commented May 3, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@jarcherNV

Copy link
Copy Markdown
Collaborator Author

/ok to test 112d572

@jarcherNV

Copy link
Copy Markdown
Collaborator Author

/ok to test 5199698

@jarcherNV

Copy link
Copy Markdown
Collaborator Author

/ok to test 8601586

env:
# Required secrets:
# GITLAB_TOKEN (PAT with write_repository + api scope)
# GITLAB_HOST (GitLab host, e.g. gitlab-master.nvidia.com)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we actually resolve the internal gitlab from "external" runners?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No it cannot, so either this would need to use a self hosted runner, or we'd need a different sync mechanism.

@janickm janickm left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

most likely what you want to do instead is to have the GL "pull" the GH changes (not the other way around) - this would also simplify the integration on this public-facing repo a lot and we wouldn't "share" internal details

[👎 for now]

@janickm janickm marked this pull request as draft May 4, 2026 11:12
@jarcherNV

Copy link
Copy Markdown
Collaborator Author

Closing this PR as we will be sync'ing from the gitlab side instead.

@jarcherNV jarcherNV closed this May 7, 2026
@jarcherNV jarcherNV deleted the dev/jarcher/autosync branch May 7, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants