- 18 10月, 2019 1 次提交
-
-
由 GitLab Bot 提交于
-
- 16 10月, 2019 1 次提交
-
-
由 GitLab Bot 提交于
-
- 10 10月, 2019 1 次提交
-
-
由 GitLab Bot 提交于
-
- 02 10月, 2019 1 次提交
-
-
由 GitLab Bot 提交于
-
- 30 9月, 2019 1 次提交
-
-
由 Fabio Pitino 提交于
This prevents a MITM attack where attacker could still access Git repository if any jobs were running long enough.
-
- 28 9月, 2019 1 次提交
-
-
由 GitLab Bot 提交于
-
- 24 9月, 2019 1 次提交
-
-
由 Fabio Pitino 提交于
This prevents a MITM attack where attacker could still access Git repository if any jobs were running long enough.
-
- 18 9月, 2019 1 次提交
-
-
由 GitLab Bot 提交于
-
- 10 9月, 2019 1 次提交
-
-
由 Ahmad Sherif 提交于
It consists of two parts: 1. Redirecting users to the configured external storage 1. Allowing the external storage to request the static object(s) on behalf of the user by means of specific tokens Part of https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6829
-
- 07 9月, 2019 1 次提交
-
-
由 Jan Provaznik 提交于
Because we don't have any destroy callbacks (or other logic triggered on event destroy), there is no reason for deleting events inefficiently one by one, instead we can use :delete_all.
-
- 28 8月, 2019 1 次提交
-
-
由 Adam Hegyi 提交于
This change sets NOT NULL constraint to users.private profile. closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57538
-
- 27 8月, 2019 1 次提交
-
-
由 Aishwarya Subramanian 提交于
Removed unused method for name setter method
-
- 21 8月, 2019 1 次提交
-
-
Devise checks before updating any of the authentication_keys if it needs to clear the reset_password_tokens. This should fix: https://gitlab.com/gitlab-org/gitlab-ce/issues/42733 (Weak authentication and session management)
-
- 05 8月, 2019 1 次提交
-
-
由 Stan Hu 提交于
-
- 25 7月, 2019 1 次提交
-
-
由 Heinrich Lee Yu 提交于
These are not required because MySQL is not supported anymore
-
- 23 7月, 2019 1 次提交
-
-
由 Heinrich Lee Yu 提交于
When a user's notification email is set for a group, we should use that for pipeline emails
-
- 16 7月, 2019 1 次提交
-
-
由 Adam Hegyi 提交于
- Background migration for changing null values to false - Set false as default value for private_profile DB column
-
- 10 7月, 2019 1 次提交
-
-
由 Bob Van Landuyt 提交于
Instead of setting the name of the namespace to the user's username, set it to the user's name. This is more consistent with how we name the routes: The route-name of a namespace is the human name of the routable. In the case of a user-namespace, this is the owner's name. When we change a user's name (both on create and update), we now also update the namespace-name to the user's name. This will make sure that if we also correctly update all the nested routes.
-
- 02 7月, 2019 2 次提交
-
-
由 Stan Hu 提交于
-
由 Stan Hu 提交于
The introduction of the in-memory cache for application settings had a side effect of making it harder to invalidate changes when the settings occur. We now bypass the cache because it's possible the admin enabled the usage ping, and we don't want to annoy the user again if they already set the value. To avoid causing significant load on the system, we add an extra check to ensure the user is an admin. and we don't want to annoy the user again if they already set the value. This is a bit of hack, but the alternative would be to put in a more complex cache invalidation step. Since this call only gets called in the uncommon situation where the user is an admin and the only user in the instance, this shouldn't cause too much load on the system.
-
- 19 6月, 2019 1 次提交
-
-
由 Kartikey Tanna 提交于
Disabled password authentication for the users registered using omniauth-ultraauth strategy
-
- 13 6月, 2019 1 次提交
-
-
由 Roger Meier 提交于
-
- 09 4月, 2019 1 次提交
-
-
由 Oswaldo Ferreira 提交于
Backports https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10161 (code out of ee/ folder).
-
- 05 4月, 2019 1 次提交
-
-
由 Brandon Labuschagne 提交于
Truncate existing users names which exceed 128 characters Include test for truncating users names
-
- 01 4月, 2019 1 次提交
-
-
由 Thong Kuah 提交于
Adds `# frozen_string_literal: true` to spec/models ruby files
-
- 22 3月, 2019 1 次提交
-
-
由 Thiago Presa 提交于
-
- 20 2月, 2019 1 次提交
-
-
由 Stan Hu 提交于
Ruby 2.6 introduced `Enumerable#filter`, which takes no arguments. Attempting to call `filter` on an `ActiveRecord::Relation` with a scope will fail with a `wrong number of arguments (given 1, expected 0)` message because the `Enumerable#filter` implementation overrides the delegated `ActiveRecord::Relation#filter` method. To make Admin::UsersController compatible with Ruby 2.6, rename `User.filter` to `User.filter_items`.
-
- 13 2月, 2019 1 次提交
-
-
由 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.
-
- 31 1月, 2019 1 次提交
-
-
由 Tiago Botelho 提交于
Group guests will only be displayed merge requests to projects they have a access level to, higher than Reporter. Visible projects will still display the merge requests to Guests
-
- 21 1月, 2019 1 次提交
-
-
由 Tiago Botelho 提交于
Group guests will only be displayed merge requests to projects they have a access level to, higher than Reporter. Visible projects will still display the merge requests to Guests
-
- 19 12月, 2018 1 次提交
-
-
由 Jarka Košanová 提交于
- we now use the hierarchy class also for epics - also rename supports_nested_groups? into supports_nested_objects? - move it to a concern
-
- 13 12月, 2018 1 次提交
-
-
由 Alessio Caiazza 提交于
This commit adds a name to each release, defaulting it to tag name, keeps track of the SHA when a new release is created and tracks the current user as release author.
-
- 07 12月, 2018 1 次提交
-
-
由 Jan Provaznik 提交于
It gathers list of file paths to delete before destroying the parent object. Then after the parent_object is destroyed these paths are scheduled for deletion asynchronously. Carrierwave needed associated model for deleting upload file. To avoid this requirement, simple Fog/File layer is used directly for file deletion, this allows us to use just a simple list of paths.
-
- 06 12月, 2018 1 次提交
-
-
由 James Lopez 提交于
Resolve "Can add an existing group member into a group project with new permissions but permissions are not overridden"
-
- 03 12月, 2018 3 次提交
-
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
- 26 11月, 2018 1 次提交
-
-
由 Imre Farkas 提交于
-
- 19 11月, 2018 1 次提交
-
-
由 Nick Thomas 提交于
Private commit emails were introduced in !22560, but some parts of GitLab were not updated to take account of them. This commit adds support in places that were missed.
-
- 07 11月, 2018 1 次提交
-
-
由 Tiago Botelho 提交于
The private commit email is automatically generated in the format: id-username@noreply.HOSTNAME GitLab instance admins are able to change the HOSTNAME portion, that defaults to Gitlab's hostname, to whatever they prefer.
-