gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2020-09-19	Add latest changes from gitlab-org/gitlab@13-4-stable-ee	GitLab Bot

2020-06-18	Add latest changes from gitlab-org/gitlab@13-1-stable-ee	GitLab Bot

2020-05-20	Add latest changes from gitlab-org/gitlab@13-0-stable-ee	GitLab Bot

2020-04-20	Add latest changes from gitlab-org/gitlab@12-10-stable-ee	GitLab Bot

2020-04-01	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2020-01-15	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-11-07	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-08-28	Remove Rubocop::SpecHelper file	Vitali Tatarintev

2019-08-28	Refactor BeSuccessMatcher specs for readability	Vitali Tatarintev

2019-08-28	Utilize Rubocop's Include for BeSuccessMatcher	Vitali Tatarintev
	Use Rubocop's Include instead of manually checking the matcher in controllers specs.
2019-08-28	Add support of not_to/to_not to BeSuccessMatcher	Vitali Tatarintev
	BeSuccessMatcher now supports following examples: ``` expect(response).to be_success expect(response).to_not be_success expect(response).not_to be_success is_expected.to be_success is_expected.to_not be_success is_expected.not_to be_success ```
2019-08-28	Replace double quotes with single quotes	Vitali Tatarintev

2019-08-28	Enable frozen string literal	Vitali Tatarintev

2019-08-28	Autocorrect `be_success` to `be_successful`	Vitali Tatarintev

2019-08-28	Add Rubocop check to avoid using `be_success`	Vitali Tatarintev
	Prevent using `be_success` call in controller specs to avoid getting following deprecation warning: ``` DEPRECATION WARNING: The success? predicate is deprecated and will be removed in Rails 6.0. Please use successful? as provided by Rack::Response::Helpers. ```
2019-08-26	Utilize RuboCop's Include/Exclude config	Peter Leitzen
	Stop checking the file location programmatically.
2019-08-01	Add RSpec/TopLevelDescribePath cop	Sean McGivern
	The RSpec/FilePath cop checks that a spec file's path is correct, but only if the file describes a constant. We want to check, for any file with a top-level `describe`, whether the file path ends in `_spec.rb`. We don't care what comes before that; just that it will be executed by RSpec at all.
2018-04-06	Introduce a new FactoriesInMigrationSpecs cop	Rémy Coutable
	Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-12-22	Use gitlab-styles	Rémy Coutable
	Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-10-18	Add a new RSpec::EnvAssignment cop to prevent assigning to ENV in specs	Rémy Coutable
	Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-10-07	Replaces `tag: true` into `:tag` in the specs	Jacopo
	Replaces all the explicit include metadata syntax in the specs (tag: true) into the implicit one (:tag). Added a cop to prevent future errors and handle autocorrection.
2017-06-15	Require rubocop-rspec in the correct location	Robert Speicher
	Resolves the `codeclimate` CI failure
2017-06-14	Add a custom RSpec/SingleLineHook cop	Robert Speicher
	This cop adds an offense when `before`, `after`, or `around` are used as single-line blocks.