An error occurred fetching the project authors.
- 29 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 28 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 21 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 19 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 18 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 14 Nov, 2019 2 commits
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- 13 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 08 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 30 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 28 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 23 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 18 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 17 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 14 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 08 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 07 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 03 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 30 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 27 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 25 Sep, 2019 2 commits
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- 18 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 16 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 13 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 09 Sep, 2019 1 commit
-
-
mo khan authored
-
- 05 Sep, 2019 2 commits
-
-
Fabio Pitino authored
Detect if pipeline runs for a GitHub pull request When using a mirror for CI/CD only we register a pull_request webhook. When a pull_request webhook is received, if the source branch SHA matches the actual head of the branch in the repository we create immediately a new pipeline for the external pull request. Otherwise we store the pull request info for when the push webhook is received. When using "only/except: external_pull_requests" we can detect if the pipeline has a open pull request on GitHub and create or not the job based on that.
- 03 Sep, 2019 2 commits
-
-
Jan Provaznik authored
Creates new event when an epic is created, closed, reopened or commented.
-
Etienne Baqué authored
Modified schema via migrations. Added one-to-one relationship between the two models. Added changelog file
-
- 28 Aug, 2019 1 commit
-
-
Felipe Artur authored
Persists if a board list is collapsed for each user.
-
- 15 Aug, 2019 1 commit
-
-
Adam Hegyi authored
This change lays the foundation for customizable cycle analytics stages. The main reason for the change is to extract the event definitions to separate objects (start_event, end_event) so that it could be easily customized later on.
-
- 07 Aug, 2019 1 commit
-
-
Tiger authored
Creating new records has been disabled, and all existing records been migrated to clusters as of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28534
-
- 02 Aug, 2019 1 commit
-
-
Jason Colyer authored
- Added Importable to models/list.rb - Did unless: :importable? on board validation - Created changelog - Modified haml to show issue boards are importable - Added needed spec tests - Modified project.json to include board information - Added relevant models to all_models - Added relevant models to import_export - Added relevant models to safe_model_attributes
-
- 22 Jul, 2019 1 commit
-
-
Yorick Peterse authored
This line is already present further down in the YAML file. In EE the line is already removed.
-
- 26 Jun, 2019 1 commit
-
-
Patrick Bajao authored
-
- 17 Jun, 2019 1 commit
-
-
Yorick Peterse authored
This backports all EE schema changes to CE, including EE migrations, ensuring both use the same schema. == Updated tests A spec related to ghost and support bot users had to be modified to make it pass. The spec in question assumes that the "support_bot" column exists when defining the spec. In the single codebase setup this is not the case, as the column is backported in a later migration. Any attempt to use a different schema version or use of "around" blocks to conditionally disable specs won't help, as reverting the backport migration would also drop the "support_bot" column. Removing the "support_bot" tests entirely appears to be the only solution. We also need to update some foreign key tests now that we have backported the EE columns. Fortunately, these changes are very minor. == Backporting migrations This commit moves EE specific migrations (except those for the Geo tracking database) and related files to CE, and also removes any traces of the ee/db directory. Some migrations had to be modified or removed, as they no longer work with the schema being backported. These migrations were all quite old, so we opted for removing them where modifying them would take too much time and effort. Some old migrations were modified in EE, while also existing in CE. In these cases we took the EE code, and in one case removed them entirely. It's not worth spending time trying to merge these changes somehow as we plan to remove old migrations around the release of 12.0, see https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
-
- 13 Jun, 2019 1 commit
-
-
Jarka Košanová authored
- create tables for storing issue trackers properties - add model and basic logic & spec
-
- 06 May, 2019 1 commit
-
-
Shinya Maeda authored
Refactor
-
- 26 Apr, 2019 1 commit
-
-
Reuben Pereira authored
This new table will be used to store the external_dashboard_url which allows users to add a link to their external dashboards (ex Grafana) to the Metrics dashboard.
-