Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pull mirroring does not work for existing repository #8

Closed
debugger89 opened this issue Jun 14, 2018 · 9 comments
Closed

Pull mirroring does not work for existing repository #8

debugger89 opened this issue Jun 14, 2018 · 9 comments
Labels
enhancement New feature or request

Comments

@debugger89
Copy link

If the mirror and the mirrored both repos existing in the gitlab there is no way to setup mirroring between them.

Use case:
For syncing fork repositories and their upstream repo, the tool is not supporting the sync.

Expected behavior:

The tool should be able to setup sync between the two existing repos (fork and original)
And the pull sync should have the merging capabilities for the fork repo

@Salamek
Copy link
Owner

Salamek commented Jun 14, 2018

@debugger89 Can you pls write down how to reproduce this ?

@Salamek Salamek added bug Something isn't working question Further information is requested labels Jun 14, 2018
@debugger89
Copy link
Author

Issue reproduce steps:

Create a project in a gitlab group as below.

Group name: Group1
Project name: ProjectMaster

Fork the ProjectMaster project using the fork button in the GitLab ui.

Now try to create a pull mirror in the tool for the two projects. Give the original ProjectMaster git repo ssh url and the the forked project name as inputs for the pull mirror.

Expected behavior:

The fork repository should be merged with the upstream and synced. (As if using git merge upstream/master and pushing the merge to origin/master)

Actual behavior:

No merge nor mirroring happen between the two repositories. And also the trigger sync button is disappearing from the pull mirror screen

@Salamek Salamek removed the question Further information is requested label Jun 14, 2018
@debugger89
Copy link
Author

@Salamek but as far as i can see this does not fix the original issue of merging the two projects. This doe the mirroring. But acts as a force push for the mirror project?
Awsome work btw

@debugger89
Copy link
Author

So this issue is not officially closed :)

@debugger89
Copy link
Author

@Salamek I tested the solution, but the mirroring is not happening between the forked repositories yet.
Trigger sync button is available in the pull mirror screen though.
I'm sorry but this issue is not resolved.

@Salamek
Copy link
Owner

Salamek commented Jun 15, 2018

@debugger89 well mirroring and merging are two differend things... and only mirroring is supported now.
But i may add differend mirror strategies like:

  • Git mirror (fetch -> push --mirror)
  • Git merge (fetch -> merge -> push, only master branch, mirror will fail on merge conflict)

Reopening issue + changing from bug to enhancement

@Salamek Salamek reopened this Jun 15, 2018
@Salamek Salamek added enhancement New feature or request and removed bug Something isn't working labels Jun 15, 2018
@debugger89
Copy link
Author

Mirror failure should be visible to the user in the UI level in order to understand the issue.

Any ETA on this?

@Salamek
Copy link
Owner

Salamek commented Jun 16, 2018

@debugger89 This depends on #1 and that depends on solving Robpol86/Flask-Celery-Helper#22 ...
I will try to look on it today

@Salamek
Copy link
Owner

Salamek commented Apr 30, 2020

This should be ~solved by #1 i think? Closing...

@Salamek Salamek closed this as completed Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants