gitlab-mirror-orchestrator merge requestshttps://gitlab.ow2.org/ow2/gitlab-mirror-orchestrator/-/merge_requests2021-10-06T07:39:09Zhttps://gitlab.ow2.org/ow2/gitlab-mirror-orchestrator/-/merge_requests/1refactoring the main loop2021-10-06T07:39:09ZMartin Hamantrefactoring the main loopThis would improve the cognitive and cyclomatic complexityThis would improve the cognitive and cyclomatic complexityMartin HamantMartin Hamanthttps://gitlab.ow2.org/ow2/gitlab-mirror-orchestrator/-/merge_requests/2Keep repository deleted or archived from GitHub in GitLab2022-06-13T15:34:12ZAntoine MottierKeep repository deleted or archived from GitHub in GitLabAs we want to archive all project content we don't want to remove a repository that is no longer part of the project (because, for example, it has been archived or deleted from GitHub). We rather want to disable the synchronization to Gi...As we want to archive all project content we don't want to remove a repository that is no longer part of the project (because, for example, it has been archived or deleted from GitHub). We rather want to disable the synchronization to GitLab and keep it archived it in GitLab.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/gitlab-mirror-orchestrator/-/merge_requests/3Try to clarify the git-mirror capabilities2022-06-13T15:51:33ZAntoine MottierTry to clarify the git-mirror capabilitiesgit-mirror handle the synchronization of a whole GitHub organization to GitLab.
It is possible to disable the synchronization of previously synchronized GitLab repository by adding: `skip: true` to the GitLab repository description.git-mirror handle the synchronization of a whole GitHub organization to GitLab.
It is possible to disable the synchronization of previously synchronized GitLab repository by adding: `skip: true` to the GitLab repository description.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/gitlab-mirror-orchestrator/-/merge_requests/5Add comments in code2022-10-31T09:31:15ZAntoine MottierAdd comments in codeAs !4 was starting to be confusing mixing addition of comments and change in code I create this new merge request to include only comments and some variables renaming in the `master` branch.As !4 was starting to be confusing mixing addition of comments and change in code I create this new merge request to include only comments and some variables renaming in the `master` branch.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/gitlab-mirror-orchestrator/-/merge_requests/6Improve source type validation2022-10-31T09:31:16ZAntoine MottierImprove source type validationThis implementation will raise an error if more than one source type is provided for a given item. Previous implementation was raising an error if all source type were provided (this is valid with two source types but will break if we ad...This implementation will raise an error if more than one source type is provided for a given item. Previous implementation was raising an error if all source type were provided (this is valid with two source types but will break if we add a third source type).
This implementation also detect lack of source type.
Add some unit test.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/gitlab-mirror-orchestrator/-/merge_requests/7Cleanup2023-09-14T08:05:20ZAlban Espié-GuillonCleanupCleanup some logs and light reformating.Cleanup some logs and light reformating.Alban Espié-GuillonAlban Espié-Guillonhttps://gitlab.ow2.org/ow2/gitlab-mirror-orchestrator/-/merge_requests/4Fix GitLab project name limitation2023-09-14T08:06:28ZAntoine MottierFix GitLab project name limitationSolution proposed here (more a workaround) is to remove leading dot character from GitHub repository name to get a name compatible with GitLab constraints.
This should close #14 or at least partially solve it.
It might have unwanted si...Solution proposed here (more a workaround) is to remove leading dot character from GitHub repository name to get a name compatible with GitLab constraints.
This should close #14 or at least partially solve it.
It might have unwanted side effect when `only` setting is used that would need some attention while reviewing this merge request.Martin HamantMartin Hamant