- Sep 06, 2019
-
- Sep 05, 2019
-
-
Sean McGivern authored
Resolve "user-content.gitlab-static.net brings back 404 only" See merge request gitlab-org/gitlab-ce!32703 (cherry picked from commit 0e335ec9) 921c704f Set asset_proxy_whitelist default to gitlab host
-
Mayra Cabrera authored
Bring method back that was mistakenly removed See merge request gitlab-org/gitlab-ce!32667 (cherry picked from commit 0fad0ed8) 0a9cc6ab Bring method back that was mistakenly removed
-
Thong Kuah authored
Avoid checking dns rebind protection in validation Closes #66723 See merge request gitlab-org/gitlab-ce!32577 (cherry picked from commit 4e9c531a) 8f07ba0d Avoid checking dns rebind protection in validation
-
Thong Kuah authored
Allow not resolvable urls when dns rebinding setting is disabled See merge request gitlab-org/gitlab-ce!32523 (cherry picked from commit 86a3d822) aab94e7b Allow not resolvable urls when rebinding setting is disabled
-
- Sep 04, 2019
-
-
Grzegorz Bizon authored
Persist `needs:` validation as config error See merge request gitlab-org/gitlab-ce!32648 (cherry picked from commit 0da3257c) 0a39a3d4 Persist `needs:` validation as config error
-
- Sep 02, 2019
-
-
Grzegorz Bizon authored
Fix permissions check in `RelativeLinkFilter` See merge request gitlab-org/gitlab-ce!32448 (cherry picked from commit 60fd4217) be0f039d Fix upload URLs in Markdown
-
- Aug 30, 2019
-
-
Arun Kumar Mohan authored
Previously, the `showStagedIcon` property was doing the opposite of what its name suggested. It was rendering the staged icon when `showStagedIcon` was `false` and rendering the regular icon when it was `true`.
-
Updates frontend code and specs to allow for the new feature flag
-
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/56295Jesse Hall authored
All avatars now visible in commit trailers.
-
Andrew Newdigate authored
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 authored
This does not support upgrading from earlier versions
-
Shinya Maeda authored
When deployable is nil, we gracefully take care of the case.
-
Rename epic column state to state_id to be consistent with issues and merge requests
-
Markus Koller authored
- 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
-
-
Andreas Brandl authored
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.
-
This allows the be_url matcher to be more specific. By default, it only matches HTTP and HTTPS URIs.
-
- Aug 29, 2019
-
-
dineshpanda authored
-
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 authored
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
-
-
Maneschi Romain authored
-
Extract duplicated code from two similar classes into a parent one.
-
Nick Thomas authored
This reverts commit 0eff75fa.
-
George Koltsov authored
-
-
Balasankar C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
Patrick Bajao authored
Utilize the auto repair functionality of system checks.
-
Patrick Bajao authored
-
Patrick Bajao authored
This check is being removed from gitlab-shell as the file is now being managed by gitlab-rails.
-
Patrick Bajao authored
-
Stan Hu authored
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 authored
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 authored
It should not be a start to a new thread but rather a reply to an existing thread
-
Heinrich Lee Yu authored
Changes the document event listener to listen to mousedown instead of click
-
- Aug 28, 2019
-
-
Michael Kozono authored
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
-