delta/gitlab/gitlab-ce.git/app/services/users, branch bootstrap-markdown-code-highlight

Cleanly handle plural name for ghost user migration

2018-05-08T03:38:05+00:00

Allow a user to accept/decline terms

2018-05-04T11:54:43+00:00

When a user accepts, we store this in the agreements to keep track of
which terms they accepted. We also update the flag on the user.

Backport relevant changes from EE https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4827 to CE

2018-03-07T17:01:32+00:00

use Gitlab::UserSettings directly as a singleton instead of including/extending it

2018-02-02T18:39:55+00:00

Remove soft removals related code

2018-01-08T16:04:45+00:00

This removes all usage of soft removals except for the "pending delete"
system implemented for projects. This in turn simplifies all the query
plans of the models that used soft removals. Since we don't really use
soft removals for anything useful there's no point in keeping it around.

This _does_ mean that hard removals of issues (which only admins can do
if I'm not mistaken) can influence the "iid" values, but that code is
broken to begin with. More on this (and how to fix it) can be found in
https://gitlab.com/gitlab-org/gitlab-ce/issues/31114.

Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37447

Fix user membership destroy relation

2018-01-02T15:06:44+00:00

Allow password authentication to be disabled entirely

2017-11-23T13:16:14+00:00

Cache the number of user SSH keys

2017-11-16T13:59:38+00:00

By caching the number of personal SSH keys we reduce the number of
queries necessary on pages such as ProjectsController#show (which can
end up querying this data multiple times).

The cache is refreshed/flushed whenever an SSH key is added, removed, or
when a user is removed.

Refactor issuable destroy action

2017-11-06T12:02:50+00:00

Only cache the event for the fork-source when it exists

2017-10-22T17:24:47+00:00

It is possible for a fork not to have a source anymore, in this case
we don't need to keep track of the push event.