- 29 Nov, 2017 1 commit
-
-
Andrew Newdigate authored
-
- 23 Nov, 2017 1 commit
-
-
Markus Koller authored
-
- 17 Nov, 2017 1 commit
-
-
Michael Kozono authored
-
- 30 Oct, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 23 Oct, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 21 Oct, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 19 Oct, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 17 Oct, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 16 Oct, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 11 Sep, 2017 1 commit
-
-
Alex Lossent authored
This enables skipping a lesser housekeeping task (incremental or full repack) by consistently scheduling a higher task (respectively full repack or gc) with the same period. Cf. #34981
-
- 09 Sep, 2017 1 commit
-
-
Visay Keo authored
-
- 30 Aug, 2017 5 commits
-
-
Nick Thomas authored
-
Nick Thomas authored
-
Nick Thomas authored
-
Nick Thomas authored
`allowed_key_types` is removed and the `minimum_<type>_bits` fields are renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies that the key type is disabled. This also feeds through to the UI - checkboxes per key type are out, inline selection of "forbidden" and "allowed" (i.e., no restrictions) are in. As with the previous model, unknown key types are disallowed, even if the underlying ssh daemon happens to support them. The defaults have also been changed from the lowest known bit size to "no restriction". So if someone does happen to have a 768-bit RSA key, it will continue to work on upgrade, at least until the administrator restricts them.
-
Nick Thomas authored
This is an amalgamation of: * Cory Hinshaw: Initial implementation !5552 * Rémy Coutable: Updates !9350 * Nick Thomas: Resolve conflicts and add ED25519 support !13712
-
- 11 Aug, 2017 1 commit
-
-
Robin Bobbitt authored
-
- 27 Jul, 2017 1 commit
-
-
Bob Van Landuyt authored
In favor of the new `repository_storages`
-
- 13 Jul, 2017 1 commit
-
-
Robin Bobbitt authored
When sign-in is disabled: - skip password expiration checks - prevent password reset requests - don’t show Password tab in User Settings - don’t allow login with username/password for Git over HTTP requests - render 404 on requests to Profiles::PasswordsController
-
- 10 Jul, 2017 1 commit
-
-
Nick Thomas authored
-
- 07 Jul, 2017 1 commit
-
-
Rémy Coutable authored
The implementation now simply rely on the `performance_bar_allowed_group_id` Application Setting. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 06 Jul, 2017 2 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Yorick Peterse authored
This cop has been renamed to ActiveRecordSerialize to match the way "ActiveRecord" is usually written.
-
- 14 Jun, 2017 1 commit
-
-
Robin Bobbitt authored
-
- 06 Jun, 2017 1 commit
-
-
Paul Charlton authored
-
- 05 Jun, 2017 1 commit
-
-
Tiago Botelho authored
-
- 02 Jun, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 31 May, 2017 1 commit
-
-
Yorick Peterse authored
This Cop blacklists the use of ActiveRecord's "serialize" method, except for cases where we already use this.
-
- 11 May, 2017 1 commit
-
-
Sean McGivern authored
Setting `usage_ping_enabled` to false in `gitlab.yml`: 1. Disables the usage ping, regardless of the value stored in the database. 2. Prevents the usage ping from being enabled through the admin panel. It can only be enabled by either removing the line from `gitlab.yml` and configuring through the admin panel, or setting it to true in `gitlab.yml`.
-
- 28 Apr, 2017 1 commit
-
-
Luke "Jared" Bennett authored
-
- 26 Apr, 2017 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 14 Apr, 2017 1 commit
-
-
Sean McGivern authored
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/557
-
- 03 Apr, 2017 1 commit
-
-
Adam Niedzielski authored
Implement module for setting "Poll-Interval" response header. Return 429 in ETag caching middleware when polling is disabled.
-
- 22 Mar, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 18 Mar, 2017 1 commit
-
-
Stan Hu authored
Due to a Rails bug, fetching the application settings from Redis may prevent the attribute methods from being loaded for the `ApplicationSetting` model. More details here: https://github.com/rails/rails/issues/27348 There was also a secondary problem introduced by overriding these association methods which caused all default visibility levels to be set to `nil`. Before, the previous implementation allowed the string "20" to be saved as an integer, while now a table lookup happens before that. We fix this by enforcing the integer value in the controller and default to PRIVATE. Closes #29674
-
- 06 Mar, 2017 2 commits
-
-
Pawel Chojnacki authored
-
Pawel Chojnacki authored
-
- 02 Mar, 2017 2 commits
-
-
Toon Claes authored
Override the `ApplicationSetting` default visibility_level setters so they accept strings & integers for the levels.
-
Toon Claes authored
Use strings for the ApplicationSetting properties: - restricted_visibility_levels - default_project_visibility - default_snippet_visibility - default_group_visibility
-
- 24 Feb, 2017 1 commit
-