- 11 Oct, 2017 2 commits
-
-
Annabel Dunstone Gray authored
-
Annabel Dunstone Gray authored
-
- 15 Aug, 2017 1 commit
-
-
Z.J. van de Weg authored
Related to !13108. Mostly this is just running the rake task and changing the task a bit to catch cases like the project already existing or so. The rake task moves archives to the vendor/project_template directory, which are checked in too.
-
- 01 Aug, 2017 3 commits
-
-
Z.J. van de Weg authored
First round of review, main changes: - templates.title is human readable, #name will be passed around - GitLabProjectImporterService has been renamed
-
Filipa Lacerda authored
-
Z.J. van de Weg authored
First iteration, and some stuff is missing. But basically this rake task does a clone of a project we've pointed it to. Than creates a project on the GDK, which should be running in the background. This project is exported, after which we move that archive to the location we need it. We clean up by removing the generated project. The first idea was to export the project on .com too, however than we might run into ImportExport versions mismatch. This could've been circumvented by checkout out an older commit locally. This however is not needed yet, so we opted to not go this route yet, instead we will iterate on what we got.
-
- 28 Jul, 2017 1 commit
-
-
Z.J. van de Weg authored
Started implementation for the first iteration of gitlab-org/gitlab-ce#32420. This will allow users to select a template to start with, instead of an empty repository in the project just created. Internally this is basically a small extension of the ImportExport GitLab projects we already support. We just import a certain import tar archive. This commits includes the first one: Ruby on Rails. In the future more will be added.
-