- 06 Jul, 2017 40 commits
-
-
Nick Thomas authored
-
Nick Thomas authored
-
Nick Thomas authored
-
Nick Thomas authored
-
Nick Thomas authored
-
Filipa Lacerda authored
Limit the file tree view container width Closes #34670 See merge request !12643
-
Marin Jankovski authored
Add GitLab Runner Helm Chart documenation for custom certificates See merge request !12594
-
Valery Sizov authored
-
Kamil Trzciński authored
Re-enable polling for environments See merge request !12678
-
Sean McGivern authored
Backport Service changes from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2259 See merge request !12653
-
Tim Zallmann authored
Cleanup minor UX issues in the performance dashboard Closes #34653 See merge request !12635
-
Filipa Lacerda authored
-
Phil Hughes authored
Revert "Merge branch 'winh-mr-widget-no-pipeline' into 'master'" See merge request !12674
-
Valery Sizov authored
-
Douwe Maan authored
Backports for ee-2112 Closes #34716 See merge request !12671
-
Douwe Maan authored
Add Traditional Chinese in Taiwan translations of Commits Page See merge request !12407
-
Kamil Trzciński authored
Generate KUBECONFIG in KubernetesService#predefined_variables Closes #33360 See merge request !12223
-
Douwe Maan authored
Fix EE conflicts for 'Fix `migration:path` build for "Honor the 'Remember me' parameter for OAuth-based login"' See merge request !2355
-
Douwe Maan authored
Fix `migration:path` build for "Honor the 'Remember me' parameter for OAuth-based login" Closes #34713 See merge request !12668
-
Marin Jankovski authored
Update alpha database documentation to reflect change in attribute See merge request !2252
-
Phil Hughes authored
Improve state management for deploy boards with realtime data Closes #2677 See merge request !2311
-
Filipa Lacerda authored
-
Jose Ivan Vargas authored
-
Sean McGivern authored
EE: Add foreign keys to various tables that point to the "projects" table See merge request !2223
-
Sean McGivern authored
Add foreign keys to various tables that point to the "projects" table See merge request !9388
-
Job van der Voort authored
Add overview and use cases for db load balancing docs See merge request !2342
-
Achilleas Pipinellis authored
-
Lin Jen-Shin authored
-
Tim Zallmann authored
Update Prometheus Metrics Library See merge request !12621
-
Rémy Coutable authored
Fix stubbing attributes alongside cache_markdown_field Closes #34698 See merge request !12661
-
Kamil Trzciński authored
This reverts merge request !12127
-
Yorick Peterse authored
This cop has been renamed to ActiveRecordSerialize to match the way "ActiveRecord" is usually written.
-
Yorick Peterse authored
These IDs point to non-existing rows, causing the foreign key constraints to fail.
-
Yorick Peterse authored
This is allowed for existing instances so we don't end up 76 offenses right away, but for new code one should _only_ use this if they _have_ to remove non database data. Even then it's usually better to do this in a service class as this gives you more control over how to remove the data (e.g. in bulk).
-
Yorick Peterse authored
This removes the need for relying on Rails' "dependent" option for data removal, which is _incredibly_ slow (even when using :delete_all) when deleting large amounts of data. This also ensures data consistency is enforced on DB level and not on application level (something Rails is really bad at). This commit also includes various migrations to add foreign keys to tables that eventually point to "projects" to ensure no rows get orphaned upon removing a project.
-
Yorick Peterse authored
This cop has been renamed to ActiveRecordSerialize to match the way "ActiveRecord" is usually written.
-
Yorick Peterse authored
These are specific to EE and a whole bunch of these can be fixed by just removing the `dependent:` option since we now have more foreign keys in place.
-
Yorick Peterse authored
This adds various missing foreign keys (with cascading deletes) that either point directly or indirectly to the "projects" table.
-
Yorick Peterse authored
These IDs point to non-existing rows, causing the foreign key constraints to fail.
-
Yorick Peterse authored
This is allowed for existing instances so we don't end up 76 offenses right away, but for new code one should _only_ use this if they _have_ to remove non database data. Even then it's usually better to do this in a service class as this gives you more control over how to remove the data (e.g. in bulk).
-