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

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

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

2019-07-31	Add captcha if there are multiple failed login attempts	Małgorzata Ksionek
	Add method to store session ids by ip Add new specs for storing session ids Add cleaning up records after login Add retrieving anonymous sessions Add login recaptcha setting Add new setting to sessions controller Add conditions for showing captcha Add sessions controller specs Add admin settings specs for login protection Add new settings to api Add stub to devise spec Add new translation key Add cr remarks Rename class call Add cr remarks Change if-clause for consistency Add cr remarks Add code review remarks Refactor AnonymousSession class Add changelog entry Move AnonymousSession class to lib Move store unauthenticated sessions to sessions controller Move link to recaptcha info Regenerate text file Improve copy on the spam page Change action filter for storing anonymous sessions Fix rubocop offences Add code review remarks
2019-03-08	Apply recaptcha API changes in 4.0	Toon Claes
	In recaptcha 4.0.0 there was an API change: - `public_key` -> `site_key` - `private_key` -> secret_key See: https://github.com/ambethia/recaptcha/blob/master/CHANGELOG.md
2018-10-22	Enable frozen string for lib/gitlab/*.rb	gfyoung

2018-02-02	use Gitlab::UserSettings directly as a singleton instead of ↵	Mario de la Ossa
	including/extending it
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-02-07	Use reCaptcha when an issue identified as spam	Jarka Kadlecova

2015-12-28	reCAPTCHA is configurable through Admin Settings, no reload needed.	Gabriel Mazetto