- Feb 20, 2020
-
-
GitLab Bot authored
-
- Feb 06, 2020
-
-
GitLab Bot authored
-
- Feb 05, 2020
-
-
GitLab Bot authored
-
- Feb 04, 2020
-
-
GitLab Bot authored
-
- Jan 29, 2020
-
-
GitLab Bot authored
-
- Jan 20, 2020
-
-
GitLab Bot authored
-
- Jan 16, 2020
-
-
GitLab Bot authored
-
- Jan 09, 2020
-
-
GitLab Bot authored
-
- Jan 06, 2020
-
-
GitLab Bot authored
-
- Dec 22, 2019
-
-
GitLab Bot authored
-
- Dec 20, 2019
-
-
GitLab Bot authored
-
- Dec 17, 2019
-
-
GitLab Bot authored
-
- Dec 11, 2019
-
-
GitLab Bot authored
-
- Nov 15, 2019
-
-
GitLab Bot authored
-
- Nov 12, 2019
-
-
GitLab Bot authored
-
- Oct 31, 2019
-
-
GitLab Bot authored
-
- Oct 08, 2019
-
-
GitLab Bot authored
-
- Oct 03, 2019
-
-
GitLab Bot authored
-
- Sep 19, 2019
-
-
GitLab Bot authored
-
- Sep 18, 2019
-
-
GitLab Bot authored
-
- Aug 28, 2019
-
-
Arun Kumar Mohan authored
-
- Aug 22, 2019
-
-
Stan Hu authored
`ActiveSupport::Cache::RedisCacheStore` is not compatible with the version of Rack Attack we are using (v4.4.1) per https://github.com/kickstarter/rack-attack/issues/281. Users that had rate limits enabled might see `Redis::CommandError: ERR value is not an integer or out of range` because the `raw` parameter wasn't passed along properly. As a result, the Rack Attack entry would be stored as an `ActiveSupport::Cache::Entry` instead of a raw string holding an integer value. Let's partially revert the change in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30966 to use the original cache store until we can update to Rack Attack v5.2.3 that has support for `ActiveSupport::Cache::RedisCacheStore` via https://github.com/kickstarter/rack-attack/pull/350. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66449
-
- Aug 12, 2019
-
-
Heinrich Lee Yu authored
Old cookies are still valid and are automatically upgraded by Rails
-
- Aug 08, 2019
-
-
dineshpanda authored
-
- Aug 05, 2019
-
-
Stan Hu authored
This is the first step in providing a fault-tolerant and distributed Redis caching store. We disable compression to avoid introducing a change that could have an adverse effect in production. Note that we won't be able to take advantage of the fault-tolerance and distributed features yet until we solve https://gitlab.com/gitlab-org/gitlab-ce/issues/64829. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64794
-
- Jul 30, 2019
-
-
Sean McGivern authored
These can contain sensitive content.
-
- Jul 23, 2019
-
-
Nick Thomas authored
None of this code can be reached any more, so it can all be removed
-
- Jul 22, 2019
-
-
Mike Greiling authored
-
Lukas Eipert authored
-
- Jul 12, 2019
-
-
Heinrich Lee Yu authored
Updates changed method names and fixes spec failures
-
- Jul 08, 2019
-
-
Robert Speicher authored
We use the `Gitlab.ee` and `.ee?` methods in several initializers now.
-
- Jun 17, 2019
-
-
Use gitlab_ui.scss instead of all the bootstrap imports Allow the ../node_modules path from gitlab_ui.scss to resolve
-
Yorick Peterse authored
This backports the EE changes made to this config file to CE. EE specific bits do not need an `if Gitlab.ee?`, as everything will work transparently when using CE.
-
- Apr 23, 2019
-
-
Model.new.attributes now also returns encrypted attributes.
-
- Apr 12, 2019
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- Mar 13, 2019
-
-
Heinrich Lee Yu authored
-
- Feb 22, 2019
-
-
Simon Knox authored
-
- Feb 15, 2019
-
-
Simon Knox authored
Compile highlight CSS separately Move highlight-specific mixins out of mixins.scss Rename solarized themes to match theme name as this was a smaller change than changing all instances to snake_case
-
- Feb 14, 2019
-
-
Andrew Newdigate authored
This change adds `note` to the Rails `filter_parameters` configuration.
-
- Jan 16, 2019
-
-
Jasper Maes authored
-