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@14-4-stable-eev14.4.0-rc42	GitLab Bot	2021-10-20	1	-0/+9
\|
*	Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42	GitLab Bot	2021-09-20	1	-17/+88
\|
*	Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42	GitLab Bot	2021-08-19	1	-31/+77
\|
*	Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42	GitLab Bot	2021-07-20	1	-14/+97
\|
*	Add latest changes from gitlab-org/gitlab@14-0-stable-eev14.0.0-rc42	GitLab Bot	2021-06-16	1	-0/+35
\|
*	Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42	GitLab Bot	2021-05-19	1	-51/+181
\|
*	Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43	GitLab Bot	2021-04-20	1	-68/+173
\|
*	Add latest changes from gitlab-org/gitlab@13-10-stable-eev13.10.0-rc40	GitLab Bot	2021-03-16	1	-1/+27
\|
*	Add latest changes from gitlab-org/gitlab@13-9-stable-eev13.9.0-rc42	GitLab Bot	2021-02-18	1	-253/+0
\|
*	Add latest changes from gitlab-org/gitlab@13-8-stable-eev13.8.0-rc42	Robert Speicher	2021-01-20	1	-0/+190
\|
*	Add latest changes from gitlab-org/gitlab@13-7-stable-ee	GitLab Bot	2021-01-08	1	-4/+7
\|
*	Add latest changes from gitlab-org/gitlab@13-6-stable-eev13.6.0-rc42	GitLab Bot	2020-11-19	1	-1/+1
\|
*	Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42	GitLab Bot	2020-10-21	1	-8/+335
\|
*	Add latest changes from gitlab-org/gitlab@13-4-stable-ee	GitLab Bot	2020-09-19	1	-2/+9
\|
*	Add latest changes from gitlab-org/gitlab@13-3-stable-ee	GitLab Bot	2020-09-14	1	-0/+52
\|
*	Add latest changes from gitlab-org/gitlab@13-3-stable-ee	GitLab Bot	2020-08-20	1	-1/+1
\|
*	Add latest changes from gitlab-org/gitlab@13-2-stable-ee	GitLab Bot	2020-07-20	1	-239/+49
\|
*	Add latest changes from gitlab-org/gitlab@13-1-stable-ee	GitLab Bot	2020-06-18	1	-57/+94
\|
*	Add latest changes from gitlab-org/gitlab@13-0-stable-ee	GitLab Bot	2020-05-20	1	-145/+246
\|
*	Add latest changes from gitlab-org/gitlab@12-10-stable-ee	GitLab Bot	2020-04-20	1	-0/+6
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-04-13	1	-0/+329
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-03-26	1	-0/+24
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-03-24	1	-3/+41
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-03-02	1	-33/+59
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-02-21	1	-0/+9
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-02-19	1	-0/+56
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-02-05	1	-3/+3
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-01-29	1	-1/+1
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-01-28	1	-0/+362
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-01-23	1	-0/+13
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-01-15	1	-1/+5
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-01-08	1	-0/+42
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-01-06	1	-0/+19
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2019-12-17	1	-0/+13
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2019-12-02	1	-37/+149
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2019-11-05	1	-1/+0
\|
*	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	-17/+3
\| \| \| \| \|	RailsHelpers.stub_rails_env takes care of stubbing Rails.env
*	Add helper to exactly undo cleanup_concurrent_column_rename	Reuben Pereira	2019-08-25	1	-0/+106
\| \| \| \|	- Also add helper to undo rename_column_concurrently.
*	Drop existing trigger before creating new one	Reuben Pereira	2019-08-24	1	-0/+8
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	- When renaming a column concurrently, drop any existing trigger before attempting to create a new one. When running migration specs multiple times (as it happens during local development), the down method of previous migrations are called. If any of the called methods contains a call to rename_column_concurrently, a trigger will be created and not removed. So, the next time a migration spec is run, if the same down method is executed again, it will cause an error when attempting to create the trigger (since it already exists). Dropping the trigger if it already exists will prevent this problem.
*	Add frozen_string_literal to spec/lib (part 1)	Thong Kuah	2019-07-26	1	-0/+2
\| \| \| \| \|	Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
*	Remove dead MySQL code	Nick Thomas	2019-07-23	1	-398/+144
\| \| \| \|	None of this code can be reached any more, so it can all be removed
*	Improves add_timestamps_with_timezone helper	Alex Kalderimis	2019-07-18	1	-3/+74
\| \| \| \| \| \| \| \| \|	This improves the `add_timestamps_with_timezone` helper by allowing the column names to be configured. This has the advantage that unnecessary columns can be avoided, saving space. A helper for removing the columns is also provided, to be used in the `down` method of migrations.
*	Support jsonb Default Value in add_column_with_default Migration Helper	Jason Goodman	2019-06-28	1	-0/+18
\|
*	Remove import columns from projects tablesh-remove-import-columns-from-projects	Stan Hu	2019-06-19	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21497, we migrated all project import data into a separate table, `project_import_data`. In addition, we also added: ``` ignore_column :import_status, :import_jid, :import_error ``` In https://gitlab.com/gitlab-com/gl-infra/production/issues/908, we observed some of these `import_error` columns consumed megabytes of error backtraces and caused slow loading of projects whenever a `SELECT * from projects` query loaded the row into memory. Since we have long migrated away from these columns, we can now drop these columns entirely.
*	Allow custom names for concurrent foreign keys	Yorick Peterse	2019-06-17	1	-0/+27
\| \| \| \| \|	This is necessary for backporting the EE schema to ensure backported foreign keys use the same key names.
*	Remove rails 4 support in CI, Gemfiles, bin/ and config/	Jasper Maes	2018-12-14	1	-6/+1
\|
*	Address specs failing in rails 4	Jan Provaznik	2018-11-14	1	-1/+6
\| \| \| \| \| \| \| \| \| \| \|	We want to run CI with rails 4 for a short-term (until we are sure that we will ship with rails 5). The problem is that rails 4 can not handle rails 5 schema.rb properly - specifically `t.index` directive can not handle multiple indexes on the same column. Because combination of rails 4 + rails 5 schema will be used only in CI for a short-term, we can just ignore these incompatibility failures. This patch adds `rails5` helper for specs.
*	disable_statement_timeout doesn't require any argument anymore	Gabriel Mazetto	2018-08-11	1	-43/+32
\| \| \| \| \| \| \| \| \|	it will decide the method for disable statement_timeout upon per transaction or per session, based on how it's called. When calling with a block, block will be executed and it will use session based statement_timeout, otherwise will default to existing behavior.
*	Fix migration_helpers_spec	Gabriel Mazetto	2018-08-10	1	-1/+2
\|
*	MigrationHelper `disable_statement_timeout` accepts `transaction: false`	Gabriel Mazetto	2018-08-10	1	-13/+93
\| \| \| \| \| \| \| \| \|	By default statement_timeout will only be enabled during transaction lifetime, therefore not leaking outside of it. With `transaction: false` it will set for entire session, but requires a block to passed. It yields control and cleans up session after block finishes, also preventing leaking outside of it.