- 06 3月, 2019 2 次提交
-
-
由 Bob Van Landuyt 提交于
These adjustments make sure our GraphQL helpers support rendering queries for empty fields like this: { echo(text: "Hello world") } Instead of like this: { echo(text: "Hello world") { } } The latter would be an invalid query, causing parsing errors.
-
由 Alexandru Croitor 提交于
* Support label parameter as comma separated and array of strings for merge requests and issues api endpoints
-
- 05 3月, 2019 3 次提交
-
-
由 Nick Thomas 提交于
-
由 Thong Kuah 提交于
Maybe this will help us debug https://gitlab.com/gitlab-org/gitlab-ee/issues/10154
-
由 Igor Drozdov 提交于
-
- 04 3月, 2019 3 次提交
-
-
由 Ezekiel Kigbo 提交于
Updated nav-sidebar to reflect the documented behaviour from the design.gitlab.com docs: https://design.gitlab.com/regions/navigation#contextual-navigation Updated rspec tests to reflect the expected behaviour
-
由 Ezekiel Kigbo 提交于
Adds the collapsed mixin to the styling for .nav-sidebar ensuring the nav-sidebar is collapsed on load via media queries. Removes the need for an intermediate class to collapse the sidebar on mobile viewports Updated toggleCollapsedSidebar to check for desktop breakpoint
-
由 Luke Bennett 提交于
Adds rspec view tests that expect the nav sidebar to have a class that will cause the nav sidebar to be rendered collapsed with or without js. Tests the nav sidebar on the admin, group, instance statistics, user profile and project sidebars.
-
- 28 2月, 2019 1 次提交
-
-
由 Alexandru Croitor 提交于
* Add email_header_and_footer_enabled flag to appearances table * Set email_header_and_footer_enabled default value to false * Add checkbox to appearance to toggle show header and footer in emails * Add email_header_and_footer_enabled to allowed params in controller * Add header and footer messages to the html and text email layouts * Remove the color styling for emails header and footer * Add empty_mailer layout for emails without layout, to have the header and footer applied
-
- 27 2月, 2019 4 次提交
-
-
由 Matija Čupić 提交于
This reverts commit f5201a81, reversing changes made to 48e6db0d.
-
由 Jacob Vosmaer 提交于
-
由 Kamil Trzciński 提交于
This reverts merge request !25293
-
由 João Cunha 提交于
- deletes schedule_installation_service.rb - moves schedule_installation_service.rb logic to create_service.rb - moves specs as well Removes code duplication Remove unecessary spec block Abide review suggestions Test installable applications which are not associated to a cluster Fix a typo Removes duplciated expectation Reuse variable instead of redefining Remove method in favor of a local scoped lambda Improve 'failing service' shared examples Test the increase of status count Remove duplicated test Enable fronzen literal
-
- 26 2月, 2019 2 次提交
-
-
由 Matija Čupić 提交于
This adds a concern that abstracts the concept of masking a variable, including the RegEx for validation.
-
由 Luke Duncalfe 提交于
Previously GraphQL field authorization happened like this: class ProjectType field :my_field, MyFieldType do authorize :permission end end This change allowed us to authorize like this instead: class ProjectType field :my_field, MyFieldType, authorize: :permission end A new initializer registers the `authorize` metadata keyword on GraphQL Schema Objects and Fields, and we can collect this data within the context of Instrumentation like this: field.metadata[:authorize] The previous functionality of authorize is still being used for mutations, as the #authorize method here is called at during the code that executes during the mutation, rather than when a field resolves. https://gitlab.com/gitlab-org/gitlab-ce/issues/57828
-
- 25 2月, 2019 1 次提交
-
-
由 Jarka Košanová 提交于
-
- 23 2月, 2019 1 次提交
-
-
由 Heinrich Lee Yu 提交于
Removes unneeded params from permitted list This also fixes commenting on commits with a hash starting with a large number
-
- 21 2月, 2019 2 次提交
-
-
由 Mark Chao 提交于
Previously one could move any temp/ sub folder around.
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 18 2月, 2019 1 次提交
-
-
由 Reuben Pereira 提交于
Reactive caching concern was using .present? to determine if it got a valid value from the cache. This returns false for values such as false, [], {}. Change this check to !.nil? instead.
-
- 16 2月, 2019 3 次提交
-
-
由 Nermin Vehabovic 提交于
-
由 Nermin Vehabovic 提交于
-
由 Natalia Tepluhina 提交于
- replaced file.too_large - replaced file.text - replaced file.collapsed
-
- 15 2月, 2019 3 次提交
-
-
由 João Cunha 提交于
- Adds to specs the case where apps are also updated - Rename scope calls on Gitlab::UsageData and Clusters::Cluster - Removes a duplicated spec
-
由 Thong Kuah 提交于
Given https://github.com/helm/helm/issues/3338, I think that we should exclude applications that are :update_errored, :updating as well.
-
由 Thong Kuah 提交于
This could be potentially useful to all cluster applications. Address followup issue https://gitlab.com/gitlab-org/gitlab-ce/issues/56524
-
- 14 2月, 2019 3 次提交
-
-
由 Jarka Košanová 提交于
Add project when creating milestone in specs We validate milestone is from the same project/parent group as issuable -> we need to set project in specs correctly Improve methods names and specs organization
-
由 Lin Jen-Shin 提交于
And fix the tests so that it won't run into circular paths.
-
由 Stan Hu 提交于
This reverts merge request !25173
-
- 13 2月, 2019 3 次提交
-
-
由 Robert Schilling 提交于
-
由 Shinya Maeda 提交于
Apply nice suggestions
-
由 Luke Bennett 提交于
These are backend changes. Use Vue for the import feature UI for "githubish" providers (GitHub and Gitea). Add "Go to project" button after a successful import. Use CI-style status icons and improve spacing of the table and its component. Adds ETag polling to the github and gitea import jobs endpoint.
-
- 12 2月, 2019 1 次提交
-
-
由 Jan Provaznik 提交于
Fast destroy of uploads was successfully enabled and test.
-
- 10 2月, 2019 1 次提交
-
-
由 Robert Schilling 提交于
-
- 08 2月, 2019 2 次提交
-
-
由 Thong Kuah 提交于
We can have multiple and conditional transistions in a event, so make use of that.
-
由 Thong Kuah 提交于
-
- 07 2月, 2019 1 次提交
-
-
由 Brett Walker 提交于
Allow single tasks to be updated quickly
-
- 06 2月, 2019 3 次提交
-
-
由 Thong Kuah 提交于
All applications except for Jupyter have the same #set_initial_status, so create a new shared example which we include in all application specs except for juptyer_spec. Juptyer specs already have specs for it's version of #set_initial_status
-
由 Thong Kuah 提交于
This makes this consistent with :updated. And also avoids a potential issue where an install errors which means that that the recorded version won't necessarily reflect the version that is actually installed.
-
由 Thong Kuah 提交于
Note: updating version column after :updating is not ideal in the updating -> update_erroed case. This will mean that the application now records the version as the version that failed to upgrade, not the version that it is currently on.
-