- 27 7月, 2018 2 次提交
-
-
由 Sean McGivern 提交于
This reverts merge request !20679
-
由 Bob Van Landuyt 提交于
-
- 11 7月, 2018 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 06 6月, 2018 1 次提交
-
-
由 Mark Chao 提交于
-
- 29 5月, 2018 1 次提交
-
-
由 Rémy Coutable 提交于
Ensure ApplicationSetting#performance_bar_allowed_group_id is properly set when retrieved from cache Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 28 5月, 2018 1 次提交
-
-
由 Davin Walker 提交于
-
- 04 5月, 2018 1 次提交
-
-
由 Bob Van Landuyt 提交于
This allows admins to define terms in the application settings. Every time the terms are adjusted, a new version is stored and becomes the 'active' version. This allows tracking which specific version was accepted by a user.
-
- 05 1月, 2018 1 次提交
-
-
由 Gauthier Wallet 提交于
-
- 08 12月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
Moving the check out of the general requests, makes sure we don't have any slowdown in the regular requests. To keep the process performing this checks small, the check is still performed inside a unicorn. But that is called from a process running on the same server. Because the checks are now done outside normal request, we can have a simpler failure strategy: The check is now performed in the background every `circuitbreaker_check_interval`. Failures are logged in redis. The failures are reset when the check succeeds. Per check we will try `circuitbreaker_access_retries` times within `circuitbreaker_storage_timeout` seconds. When the number of failures exceeds `circuitbreaker_failure_count_threshold`, we will block access to the storage. After `failure_reset_time` of no checks, we will clear the stored failures. This could happen when the process that performs the checks is not running.
-
- 23 11月, 2017 1 次提交
-
-
由 Markus Koller 提交于
-
- 21 11月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
No-one is allowed to force push to a protected branch, or delete it. That's correct in the documentation, but was wrong in the drop-down.
-
- 23 10月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
-
- 17 10月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
-
- 13 10月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
-
- 31 8月, 2017 2 次提交
-
-
由 Nick Thomas 提交于
`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 提交于
This is an amalgamation of: * Cory Hinshaw: Initial implementation !5552 * Rémy Coutable: Updates !9350 * Nick Thomas: Resolve conflicts and add ED25519 support !13712
-
- 27 7月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
In favor of the new `repository_storages`
-
- 13 7月, 2017 1 次提交
-
-
由 Robin Bobbitt 提交于
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
-
- 11 5月, 2017 1 次提交
-
-
由 Marcia Ramos 提交于
-
- 03 4月, 2017 1 次提交
-
-
由 Adam Niedzielski 提交于
Implement module for setting "Poll-Interval" response header. Return 429 in ETag caching middleware when polling is disabled.
-
- 07 3月, 2017 1 次提交
-
-
由 Regis Freyd 提交于
-
- 02 3月, 2017 2 次提交
-
-
由 Toon Claes 提交于
Use strings for the ApplicationSetting properties: - restricted_visibility_levels - default_project_visibility - default_snippet_visibility - default_group_visibility
-
由 Robert Schilling 提交于
-
- 06 2月, 2017 1 次提交
-
-
由 Adam Niedzielski 提交于
Store the value in application settings. Expose the value to Workhorse.
-
- 12 1月, 2017 1 次提交
-
-
由 Horacio Sanson 提交于
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
-
- 29 12月, 2016 1 次提交
-
-
由 Robert Schilling 提交于
-
- 04 11月, 2016 1 次提交
-
-
由 Nick Thomas 提交于
-
- 30 9月, 2016 1 次提交
-
-
由 DJ Mountney 提交于
This will allow the Koding app to enable the integration itself once is has authorized an admin user using the application secrets.
-
- 19 8月, 2016 1 次提交
-
-
由 Benjamin Schwarze 提交于
-
- 09 8月, 2016 1 次提交
-
-
由 winniehell 提交于
-
- 20 7月, 2016 1 次提交
-
-
由 Patricio Cano 提交于
-
- 19 7月, 2016 1 次提交
-
-
由 Patricio Cano 提交于
Refactor and rename `restricted_signup_domains` to `domain_whitelist` to better conform to its behavior and newly introduced behavior.
-
- 06 7月, 2016 2 次提交
-
-
由 Patricio Cano 提交于
-
由 Patricio Cano 提交于
-
- 30 6月, 2016 1 次提交
-
-
由 Alejandro Rodríguez 提交于
-
- 05 6月, 2016 1 次提交
-
-
由 Ian Kelling 提交于
-
- 03 6月, 2016 2 次提交
-
-
由 James Lopez 提交于
This reverts commit 3e991230.
-
由 James Lopez 提交于
# Conflicts: # app/models/project.rb
-
- 31 5月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 01 4月, 2016 1 次提交
-
-
由 connorshea 提交于
I’ve removed everything related to the feature based on this commit: ce08f919f34fd8849834365 Resolves #10857.
-