Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-12-20 | Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42 | GitLab Bot | |
2021-11-18 | Add latest changes from gitlab-org/gitlab@14-5-stable-eev14.5.0-rc42 | GitLab Bot | |
2021-10-20 | Add latest changes from gitlab-org/gitlab@14-4-stable-eev14.4.0-rc42 | GitLab Bot | |
2021-09-20 | Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42 | GitLab Bot | |
2021-08-19 | Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42 | GitLab Bot | |
2021-07-20 | Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42 | GitLab Bot | |
2021-06-16 | Add latest changes from gitlab-org/gitlab@14-0-stable-eev14.0.0-rc42 | GitLab Bot | |
2021-05-19 | Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42 | GitLab Bot | |
2021-04-21 | Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43 | GitLab Bot | |
2021-03-16 | Add latest changes from gitlab-org/gitlab@13-10-stable-eev13.10.0-rc40 | GitLab Bot | |
2021-01-20 | Add latest changes from gitlab-org/gitlab@13-8-stable-eev13.8.0-rc42 | Robert Speicher | |
2020-12-17 | Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42 | GitLab Bot | |
2020-11-19 | Add latest changes from gitlab-org/gitlab@13-6-stable-eev13.6.0-rc42 | GitLab Bot | |
2020-09-19 | Add latest changes from gitlab-org/gitlab@13-4-stable-ee | GitLab Bot | |
2020-08-20 | Add latest changes from gitlab-org/gitlab@13-3-stable-ee | GitLab Bot | |
2020-07-20 | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | |
2020-06-18 | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | |
2020-04-03 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-14 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-16 | Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-80898 | GitLab Bot | |
2019-12-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-20 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-08-09 | Add a field for released_at to GH importer | Cindy Pallares 🦉 | |
2019-05-31 | Setup Phabricator import | Bob Van Landuyt | |
This sets up all the basics for importing Phabricator tasks into GitLab issues. To import all tasks from a Phabricator instance into GitLab, we'll import all of them into a new project that will have its repository disabled. The import is hooked into a regular ProjectImport setup, but similar to the GitHub parallel importer takes care of all the imports itself. In this iteration, we're importing each page of tasks in a separate sidekiq job. The first thing we do when requesting a new page of tasks is schedule the next page to be imported. But to avoid deadlocks, we only allow a single job per worker type to run at the same time. For now we're only importing basic Issue information, this should be extended to richer information. | |||
2019-05-06 | Fix issuables state_id nil when importing projects from GitHub | Felipe Artur | |
Issues and merge requests imported from GitHub are having state_id set to null. This fixes the GitHub project importer and schedule migrations to fix state_id. | |||
2019-04-07 | GitHub import: Run housekeeping after initial import | Stan Hu | |
After an initial fetch, the repository will have many loose objects and refs. Running a `git gc` will compact refs into `packed-refs` and objects into `.pack` files, which should make importing pull requests faster. Part of https://gitlab.com/gitlab-org/gitlab-ce/issues/59477 | |||
2019-03-26 | Force to recreate all diffs on import | Kamil Trzciński | |
If for whatever reason we fail to import MR data, subsequent run will fail as we try to insert duplicate data. Instead of trying to recover, lets delete all and retry again. | |||
2019-03-23 | GitHub importer: Use the project creator to create branches from forks | Stan Hu | |
The project owner may actually be a group, in which case the branch creation would fail due to a lack of username. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59396 | |||
2019-03-22 | Set proper default-branch on GitHub Import | Kamil Trzciński | |
2019-03-19 | GitHub import: Create new branches as project owner | Stan Hu | |
This avoids permission errors when importing merge requests whose authors don't have direct access to push to the main repository. | |||
2019-02-27 | Move check for nil due_on into build section of spec | Diana Stanley | |
2019-02-27 | Add test for nil due_on value during import | Diana Stanley | |
2019-02-21 | Capture due date when importing milestones from Github | Diana Stanley | |
2019-02-12 | Create the source branch for a GitHub import | Stan Hu | |
When the GitHub importer creates a merge request, it retrieves the SHA but does not actually create the source branch. This makes it impossible to merge an open merge request, particularly if the source branch were from a forked project. In that case, the branch will never exist because the original `project-name:source-branch` name is never created, nor is it a valid branch name. To prevent possible branch name conflicts, forked source branches are now renamed `github/fork/project-name/source-branch` and created when necessary. Note that we only create the source branch if the merge request is open. For projects that have many merge requests, the project would end up with a lot of possibly dead branches. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57370 | |||
2019-02-06 | Refactor use of Shell.import_repository for Wikis | Stan Hu | |
The previous behavior would pass in a list of parameters to Shell, but we can improve this by using the WikiFormatter and Project models to give us the same information. | |||
2019-02-06 | Send project name with Gitaly repository requests | Stan Hu | |
When hashed storage is in use, it's helpful to have the project name associated with the request. Closes https://gitlab.com/gitlab-org/gitaly/issues/1394 | |||
2019-01-31 | Added validations to prevent LFS object forgery | Francisco Javier López | |
2019-01-29 | Revert " Trigger iid logic from GitHub importer for merge requests." | Andreas Brandl | |
This reverts commit fb98496f49bbb324b808523ea97f0844682fe1ac. | |||
2019-01-29 | Revert "Trigger iid logic from GitHub importer for issues." | Andreas Brandl | |
This reverts commit b78a69b06c165f7a463d5e0de69030346d9d5c72. | |||
2019-01-29 | Revert "Trigger iid logic from GitHub importer for milestones." | Andreas Brandl | |
This reverts commit 358675d09f6ba0fdcc4a089c6d1da6df9ff6d092. | |||
2018-12-14 | Remove rails 4 support in CI, Gemfiles, bin/ and config/ | Jasper Maes | |
2018-11-27 | Removes all the irrelevant import related code and columns | Tiago Botelho | |
Clears the import related columns and code from the Project model over to the ProjectImportState model | |||
2018-11-14 | Address specs failing in rails 4 | Jan Provaznik | |
We want to run CI with rails 4 for a short-term (until we are sure that we will ship with rails 5). The problem is that rails 4 can not handle rails 5 schema.rb properly - specifically `t.index` directive can not handle multiple indexes on the same column. Because combination of rails 4 + rails 5 schema will be used only in CI for a short-term, we can just ignore these incompatibility failures. This patch adds `rails5` helper for specs. |