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

Age	Commit message (Collapse)	Author
2021-07-20	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2021-01-29	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

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

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

2020-02-26	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-09-25	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2018-08-29	Updates code using class_methods over module ClassMethods	Jacopo

2018-08-07	Enable more frozen string in app/models/*/.rb	gfyoung
	Partially addresses #47424.
2017-11-21	Updates based on feedback	Lin Jen-Shin

2017-09-18	Add cop to make sure we don't use ivar in a module	Lin Jen-Shin

2017-08-31	`current_application_settings` belongs on `Gitlab::CurrentSettings`	Sean McGivern
	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.
2017-08-08	Re-enable SqlInjection and CommandInjection	Brian Neel

2017-07-06	Added Cop to blacklist the use of `dependent:`	Yorick Peterse
	This is allowed for existing instances so we don't end up 76 offenses right away, but for new code one should _only_ use this if they _have_ to remove non database data. Even then it's usually better to do this in a service class as this gives you more control over how to remove the data (e.g. in bulk).
2017-03-21	Present ajax call errors when failing to update an Issue	Oswaldo Ferreira

2017-02-21	Spam check and reCAPTCHA improvements	Oswaldo Ferreira

2017-02-20	Improve performance of User Agent Detail	Z.J. van de Weg

2017-02-07	Use reCaptcha when an issue identified as spam	Jarka Kadlecova

2017-02-02	Check public snippets for spam	Sean McGivern
	Apply the same spam checks to public snippets (either personal snippets that are public, or public snippets on public projects) as to issues on public projects.
2016-08-23	Also check if Akismet is enabled, before showing the `Submit as spam` button.	Patricio Cano

2016-08-16	Further refactor and syntax fixes.	Patricio Cano

2016-08-15	Refactored AkismetHelper into AkismetService and cleaned up `Spammable`	Patricio Cano
	- Refactored SpamCheckService into SpamService
2016-08-15	Allow `Issue` to be submitted as spam	Patricio Cano
	- Added controller actions as reusable concerns - Added controller tests
2016-08-15	Refactored spam related code even further	Patricio Cano
	- Removed unnecessary column from `SpamLog` - Moved creation of SpamLogs out of its own service and into SpamCheckService - Simplified code in SpamCheckService. - Moved move spam related code into Spammable concern
2016-08-15	Complete refactor of the `Spammable` concern and tests:	Patricio Cano
	- Merged `AkismetSubmittable` into `Spammable` - Clean up `SpamCheckService` - Added tests for `Spammable` - Added submit (ham or spam) options to `AkismetHelper`
2016-07-27	Refactor spam validation to a concern that can be easily reused and improve ↵	Patricio Cano
	legibility in `SpamCheckService`