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

Age	Commit message (Collapse)	Author
2022-08-26	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2022-05-13	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2022-01-07	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2021-08-23	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2021-06-28	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2021-05-17	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2020-06-24	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

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

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

2019-12-19	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-12-17	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-10-08	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

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

2019-08-30	Replace rails_helper.rb with spec_helper.rb	Ash McKenzie
	rails_helper.rb's only logic was to require spec_helper.rb.
2019-05-20	Fix specs to match route changes	Dmitriy Zaporozhets
	Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2019-01-12	Update gitlab-styles to 2.5.1	Jasper Maes

2018-10-02	Show the commit-sha for pre-release versions	Bob Van Landuyt
	The pre-release tags are set at the beginning of a release, so it would be impossible to figure out which version was running if we're running nightlies. In that case it's better to still link to the SHA. These versions don't get deployed to .com.
2018-10-01	Link to the tag from a version instead of commit	Bob Van Landuyt
	This will result in a 404 when running an unreleased security patch while still allowing users to find the commit when it is made available.
2018-09-14	Correct usage of the have_link matcher	Robert Speicher
	The second option to this matcher should be an options hash; anything else is just ignored, which can lead to false positives in tests. We see one such false positive in the "Learn more" link test in `spec/features/projects/blobs/blob_show_spec.rb`.
2018-05-24	Replace Gitlab::REVISION with Gitlab.revision and handle installations ↵	Rémy Coutable
	without a .git directory Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-10-25	Added ssh fingerprint, gitlab ci and pages information in an instance ↵	Francisco Lopez
	configuration page Closes #25142
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-06-09	Make the revision on the `/help` page clickable	Toon Claes
	For quicker access, add hyperlink to the gitlab.com commits page for the current REVISION of GitLab.
2015-09-24	Allow non-admin users to see version information	Robert Speicher
	We want users to know what features they have available (and to pressure their admins to upgrade).
2015-09-23	Move the `version_check_enabled` check from view to helper	Robert Speicher

2015-09-23	Add a view spec (gasp!) for help/index	Robert Speicher