delta/gitlab/gitlab-ce.git - gitlab.com: gitlab-org/gitlab-ce.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43	GitLab Bot	2021-04-20	1	-39/+43
\|
*	Add latest changes from gitlab-org/gitlab@13-10-stable-eev13.10.0-rc40	GitLab Bot	2021-03-16	1	-0/+14
\|
*	Add latest changes from gitlab-org/gitlab@13-2-stable-ee	GitLab Bot	2020-07-20	1	-1/+1
\|
*	Use stub_rails_env for Rails.env stubbing66966-convert-rails-env-stub-usages-to-use-railshelpers-stub_rails_env-instead	Ash McKenzie	2019-09-05	1	-5/+4
\| \| \| \| \|	RailsHelpers.stub_rails_env takes care of stubbing Rails.env
*	Add frozen_string_literal to lib part 2	Thong Kuah	2019-08-23	1	-0/+2
\| \| \| \| \|	Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
*	Disable query limiting warnings for now on GitLab.com	Stan Hu	2018-02-12	1	-4/+6
\|
*	Track and act upon the number of executed queriesquery-counts	Yorick Peterse	2018-02-01	1	-0/+65
	This ensures that we have more visibility in the number of SQL queries that are executed in web requests. The current threshold is hardcoded to 100 as we will rarely (maybe once or twice) change it. In production and development we use Sentry if enabled, in the test environment we raise an error. This feature is also only enabled in production/staging when running on GitLab.com as it's not very useful to other users.