- 01 9月, 2017 6 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
-
由 Tiago Botelho 提交于
-
由 Manolis Mavrofidis 提交于
Update to add all issues to be updated. Added functionality, proper tests, documentation and changelog.
-
由 Felipe Artur 提交于
-
由 Bryce Johnson 提交于
-
由 Eric Eastwood 提交于
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/37194 It looks like this regressed in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12601 when we switched from `fa-caret-down` to `fa-chevron-down`
-
- 31 8月, 2017 24 次提交
-
-
由 Sean McGivern 提交于
The initializers including this were doing so at the top level, so every object loaded after them had a `current_application_settings` method. However, if someone had rack-attack enabled (which was loaded before these initializers), it would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't have that method. To fix this: 1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need `Object.new.current_application_settings` to work. 2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it like that in several places. 3. Change the initializers to use that new form.
-
由 Tiago Botelho 提交于
-
由 Sean McGivern 提交于
We're going to cache the total open count separately, and then just perform these counts on the list. We already do that to get the pagination information, through Kaminari, and a future change will make Kaminari reuse the query results from earlier in the request.
-
由 Filipa Lacerda 提交于
-
由 Phil Hughes 提交于
Closes #37022
-
由 Zeger-Jan van de Weg 提交于
In this instance its subgroups, and given we can't deploy it, we shouldn't allow it to be shown. Fixes gitlab-org/gitlab-ce#34864
-
由 Mike Greiling 提交于
-
由 Rubén Dávila 提交于
-
由 Mike Greiling 提交于
-
由 Mike Greiling 提交于
-
由 Nick Thomas 提交于
-
由 Mike Greiling 提交于
-
由 Jacopo 提交于
The special characters of a wiki title are now escaped correctly.
-
由 Nick Thomas 提交于
-
由 Nick Thomas 提交于
-
由 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 提交于
-
由 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
-
由 Mike Greiling 提交于
add notes to the disabled visibility setting string helper to ensure changes are reflected in the model as well
-
由 Mike Greiling 提交于
-
由 Kim "BKC" Carlbäcker 提交于
- `Gitlab::Shell.fetch_remote` now takes a `Gitlab::Git::Repository` instead
-
由 Clement Ho 提交于
-
由 Filipa Lacerda 提交于
-
由 Rubén Dávila 提交于
-
- 30 8月, 2017 10 次提交
-
-
由 Phil Hughes 提交于
Closes #35658
-
由 Filipa Lacerda 提交于
-
由 Lin Jen-Shin 提交于
-
由 Yorick Peterse 提交于
This ensures the issues/MR cache of the sidebar is only updated when the state or confidential flags changes, instead of changing this for every update.
-
由 Sean McGivern 提交于
Postgres lets you treat `count` as another alias for `COUNT(*)` apparently, even if that's not the actual alias used.
-
由 winh 提交于
-
由 Tim Zallmann 提交于
max-width for lazy-loaded images (this was removed in the original MR through merge resolution most probably)
-
由 Tiago Botelho 提交于
-
由 winh 提交于
-
由 Hiroyuki Sato 提交于
-