- Aug 01, 2018
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- Jul 30, 2018
-
-
Marcel Amirault authored
-
- Jul 27, 2018
-
-
Bob Van Landuyt authored
-
Sean McGivern authored
This reverts merge request !20679
-
Bob Van Landuyt authored
-
- Jul 11, 2018
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- May 30, 2018
-
-
Stan Hu authored
Identified while resolving conflicts in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5906
-
- May 29, 2018
-
-
Rémy Coutable authored
Ensure ApplicationSetting#performance_bar_allowed_group_id is properly set when retrieved from cache Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- May 28, 2018
-
-
Davin Walker authored
-
- May 23, 2018
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- Feb 22, 2018
-
-
Bob Van Landuyt authored
-
- Nov 29, 2017
-
-
Andrew Newdigate authored
-
- Nov 23, 2017
-
-
Pawel Chojnacki authored
-
Pawel Chojnacki authored
-
-
- Aug 30, 2017
-
-
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
-
- Aug 11, 2017
-
-
Robin Bobbitt authored
-
- Jul 27, 2017
-
-
Bob Van Landuyt authored
In favor of the new `repository_storages`
-
Bob Van Landuyt authored
-
- Jul 13, 2017
-
-
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
-
- Jun 14, 2017
-
-
Robin Bobbitt authored
-
- Jun 02, 2017
-
-
Pawel Chojnacki authored
-
- Apr 28, 2017
-
-
Luke "Jared" Bennett authored
-
- Apr 10, 2017
-
-
Oswaldo Ferreir authored
-
- Apr 03, 2017
-
-
Adam Niedzielski authored
Implement module for setting "Poll-Interval" response header. Return 429 in ETag caching middleware when polling is disabled.
-
- Mar 02, 2017
-
-
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
-
- Feb 15, 2017
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
TODO: Add tests and screenshots
-
- Feb 06, 2017
-
-
Adam Niedzielski authored
Store the value in application settings. Expose the value to Workhorse.
-
- Feb 02, 2017
-
-
James Edwards-Jones authored
-
- Jan 12, 2017
-
-
Horacio Sanson authored
This MR enables rendering of PlantUML diagrams in Asciidoc documents. To add a PlantUML diagram all we need is to include a plantuml block like: ``` [plantuml, id="myDiagram", width="100px", height="100px"] -- bob -> alice : ping alice -> bob : pong -- ``` The plantuml block is substituted by an HTML img element with *src* pointing to an external PlantUML server. This MR also add a PlantUML integration section to the Administrator -> Settings page to configure the PlantUML rendering service and to enable/disable it. Closes: #17603
-
- Dec 29, 2016
-
-
Robert Schilling authored
-
- Nov 04, 2016
-
-
Nick Thomas authored
-
- Jul 06, 2015
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- Jul 03, 2015
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-