delta/gitlab/gitlab-ce.git/spec/views/admin, branch docs/https-many-docs-links gitlab.com: gitlab-org/gitlab-ce.git Fix fast admin counters not working when PostgreSQL has secondaries 2018-05-26T05:58:43+00:00 Stan Hu stanhu@gmail.com 2018-05-25T21:28:16+00:00 b6125f7045d2bed4aadf798dde4c547e2047e039 This commit does a number of things: 1. Reduces the number of queries needed by perform a single query to get all the tuples for the relevant rows. 2. Uses a transaction to query the tuple counts to ensure that the data is retrieved from the primary. Closes #46742 
This commit does a number of things:

1. Reduces the number of queries needed by perform a single query to get all
the tuples for the relevant rows.

2. Uses a transaction to query the tuple counts to ensure that the data
is retrieved from the primary.

Closes #46742
Replace Gitlab::REVISION with Gitlab.revision and handle installations without a .git directory 2018-05-24T08:14:01+00:00 Rémy Coutable remy@rymai.me 2018-05-24T07:57:54+00:00 d50a80a282b2ca145841774f4be154a977cccfd8 Signed-off-by: Rémy Coutable <remy@rymai.me> 
Signed-off-by: Rémy Coutable <remy@rymai.me>
Include git SHA with GitLab version 2018-04-12T05:05:09+00:00 Ash McKenzie amckenzie@gitlab.com 2018-04-12T03:33:38+00:00 a3234f410ebb0a592bed68fe8b2cf7fd7a8678c9 






`current_application_settings` belongs on `Gitlab::CurrentSettings`
2017-08-31T12:38:33+00:00

Sean McGivern
sean@gitlab.com

2017-08-31T09:47:03+00:00

5883ce95efcc4cc04f949f9b4e66d73fbede94e2

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.





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.







Change all `:empty_project` to `:project`
2017-08-02T21:47:31+00:00

Robert Speicher
rspeicher@gmail.com

2017-08-02T19:55:11+00:00

72a7b30c9f363063449b28aa9efc3a26a1752f9f












Upgrade Devise from 4.1.1 to 4.2.0.
2016-09-28T02:08:49+00:00

Connor Shea
connor.james.shea@gmail.com

2016-09-21T23:06:33+00:00

8062380f60df576478677e9819ff602303166e4d

This fixes an issue with Rails 5 and brings us up-to-date with the latest Devise release.

This also replaces the deprecated Devise::TestHelpers with Devise::Test::ControllerHelpers.

Changelog: https://github.com/plataformatec/devise/blob/v4.2.0/CHANGELOG.md#420---2016-07-01





This fixes an issue with Rails 5 and brings us up-to-date with the latest Devise release.

This also replaces the deprecated Devise::TestHelpers with Devise::Test::ControllerHelpers.

Changelog: https://github.com/plataformatec/devise/blob/v4.2.0/CHANGELOG.md#420---2016-07-01







Add gitlab-workhorse version to admin dashboard
2016-07-23T04:56:32+00:00

Katarzyna Kobierska
kkobierska@gmail.com

2016-07-18T11:58:08+00:00

10d9df28ec3b494361abcee27ffddece580bbf3a

Test for showing GitLab Workhorse version on Admin Dashboard

Refactoring





Test for showing GitLab Workhorse version on Admin Dashboard

Refactoring