- 31 8月, 2019 3 次提交
-
-
由 Filipa Lacerda 提交于
Updates frontend code and specs to allow for the new feature flag
-
由 Manoj MJ 提交于
This change limits the number of emails for new access requests notifications to 10 most recently active owners/maintainers
-
https://gitlab.com/gitlab-org/gitlab-ce/issues/56295由 Jesse Hall 提交于
All avatars now visible in commit trailers.
-
- 30 8月, 2019 17 次提交
-
-
由 Andrew Newdigate 提交于
This fixes a bug in which sidekiq histograms contain invalid labels. See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/7729 for more details.
-
由 James Fargher 提交于
This does not support upgrading from earlier versions
-
由 Shinya Maeda 提交于
When deployable is nil, we gracefully take care of the case.
-
由 Felipe Artur 提交于
Rename epic column state to state_id to be consistent with issues and merge requests
-
由 Markus Koller 提交于
- Use "results" instead of "blobs", "wiki blobs", "snippet blobs" - Use "comments" instead of "notes" - Use correct pluralization - Don't add "1 - 10 of" if there's only one page
-
由 Juliette de Rancourt 提交于
-
由 Andreas Brandl 提交于
In order to lookup a Project or Namespace by path, we prefer an exact match (case-sensitive) but in absence of that, we'd also take a case-insensitive match. The case-insensitive matching with preference for the exact match is a bit more involved in SQL as the exact lookup. Yet, the majority of cases will be an exact match. The thinking here is that we can optimize the lookup by performing an exact match first and only if there is no result, we perform the case-insensitive lookup. Data for GitLab.com: * We have about 15M records in routes table * About 2,500 routes exist where there's more than one record with the same `lower(path)` It is possible for a user to craft requests that would always trigger the 2-step search (e.g. we have a route for `/foo/bar`, the request is always for `/FOO/bar`). In this case, the change at hand is not beneficial as it would run an additional query. However, based on the data, it is highly likely that the vast majority of requests can be satisfied with an exact match only. The context for this change is https://gitlab.com/gitlab-org/gitlab-ce/issues/64590#note_208156463.
-
-
由 Alex Kalderimis 提交于
This allows the be_url matcher to be more specific. By default, it only matches HTTP and HTTPS URIs.
-
由 Sarah Yasonik 提交于
Adds a slash command in slach for closing issues. See https://docs.gitlab.com/ee/integration/slash_commands.html for documentation on the wider feature set.
-
由 Stan Hu 提交于
Previously submitting a DELETE request to an issuable URL would be enough to destroy it, but this should require human confirmation. We now require that the `destroy_confirm` parameter is set to a truthy value before this can complete. In addition, we log a Sentry error if a deletion arrived without confirmation. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/62387
-
由 Yuping Zuo 提交于
-
由 Maneschi Romain 提交于
-
由 João Cunha 提交于
Extract duplicated code from two similar classes into a parent one.
-
由 Nick Thomas 提交于
This reverts commit 0eff75fa.
-
由 George Koltsov 提交于
-
由 Lee Tickett 提交于
-
- 29 8月, 2019 16 次提交
-
-
由 Balasankar "Balu" C 提交于
Signed-off-by: NBalasankar "Balu" C <balasankar@gitlab.com>
-
由 Patrick Bajao 提交于
Utilize the auto repair functionality of system checks.
-
由 Patrick Bajao 提交于
-
由 Patrick Bajao 提交于
This check is being removed from gitlab-shell as the file is now being managed by gitlab-rails.
-
由 Patrick Bajao 提交于
-
由 Stan Hu 提交于
There was some confusion over whether `code` or `content` is the right parameter for snippets. Internally, the database stores `content`. However: 1. Project snippets use `code`. `code` gets remapped in `content` in `lib/api/project_snippets.rb`. 2. Personal snippets use `content`. To unify these APIs, allow an alias of `content` to work for project snippets. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66673
-
由 Stan Hu 提交于
When a restricted visibility level of `private` is set in the instance, creating a snippet with the `visibility` level would always fail. This happened because: 1. `params[:visibility]` was a string (e.g. "public") 2. `CreateSnippetService` and `UpdateSnippetService` only looked at `params[:visibility_level]`, which was `nil`. To fix this, we: 1. Make `CreateSnippetService` look at the newly-built `snippet.visibility_level`, since the right value is assigned by the `VisibilityLevel#visibility=` method. 2. Modify `UpdateSnippetService` to handle both `visibility_level` and `visibility` parameters. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66050
-
由 Heinrich Lee Yu 提交于
It should not be a start to a new thread but rather a reply to an existing thread
-
由 Heinrich Lee Yu 提交于
Changes the document event listener to listen to mousedown instead of click
-
由 Michael Kozono 提交于
Instead of sending varied data to Gitaly, and making Gitaly construct various messages, build the messages first and have Gitaly print either basic messages or alert messages, in the order they come. Depends on https://gitlab.com/gitlab-org/gitaly/merge_requests/1410
-
由 Sean McGivern 提交于
-
由 Igor 提交于
- Extract MR fields for notes into a separate serializer - Check if pipelines are empty via count
-
由 Felipe Artur 提交于
Persists if a board list is collapsed for each user.
-
由 Illya Klymov 提交于
-
由 Nathan Friend 提交于
This commit adds an id attribute to release blocks to allow them to be targeted as anchor links.
-
由 Jacob Vosmaer 提交于
-
- 28 8月, 2019 4 次提交
-
-
由 Jacopo 提交于
-
由 Sean McGivern 提交于
This key is useful to reduce the amount of logic needed on the frontend: if `has_warnings` is true, then the frontend knows that the request in question has warnings for some metric.
-
由 Sean McGivern 提交于
For each DetailedView subclass, we add a `warnings` array to: 1. The top-level response. 2. Each individual call under the `details` key. We use the `.thresholds` hash on the DetailedView to determine what's a warning. If that hash is empty (the default), then the warnings array will always be empty.
-
由 Yorick Peterse 提交于
This ensures the InjectEnterpriseEditionModule cop is able to detect the prepend patterns used in the qa/ directory. Previously it would not detect them as all EE QA modules reside in QA::EE, and not the top-level EE namespace.
-