summaryrefslogtreecommitdiff
path: root/spec/models/project_feature_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42GitLab Bot2020-12-171-1/+1
|
* Add latest changes from gitlab-org/gitlab@13-2-stable-eeGitLab Bot2020-07-201-1/+1
|
* Add latest changes from gitlab-org/gitlab@13-1-stable-eeGitLab Bot2020-06-181-131/+0
|
* Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot2020-05-201-25/+49
|
* Add latest changes from gitlab-org/gitlab@12-10-stable-eeGitLab Bot2020-04-201-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-141-33/+51
|
* Internalize private project minimum access levelMark Chao2019-11-251-0/+24
| | | | | Some feature allows GUEST to access only if project is not private. This method returns access level when targeting private projects.
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-021-0/+24
|
* Add tests for ProjectFeature's #public_pages? and #private_pages?61927-pages-custom-domain-virtual-domainKrasimir Angelov2019-09-111-0/+54
|
* Further remove code branches by database typeAndreas Brandl2019-07-291-5/+1
| | | | | | | | We dropped MySQL support and a lot of mysql specific code has been removed in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/29608. This comes in from the other direction and removes any `if postgresql?` branches.
* Fix wrong pages access level defaultVladimir Shushlin2019-07-171-0/+28
| | | | | - Set access level in before_validation hook - Add post migration for updating existing project_features
* Add # frozen_string_literal to spec/modelsThong Kuah2019-04-011-0/+2
| | | | Adds `# frozen_string_literal: true` to spec/models ruby files
* Make GitLab pages support access controlTuomo Ala-Vannesluoma2018-10-051-1/+14
|
* Add ProjectFeature check for feature flagRobert Speicher2018-10-041-0/+16
| | | | | | | | This will allow an explicitly-disabled feature flag to override a feature being available for a project. As an extreme example, we could quickly disable issues across all projects at runtime by running `Feature.disable(:issues)`.
* Geo: sync disabled wikis. Stage 2follow-up-geo-sync-disabled-wikisValery Sizov2018-09-251-42/+0
| | | | | | | We started syncing all the wiki regardless of the fact it's disabled or not. We couldn't do that in one stage because of needing of smoth update and deprecating things. This is the second stage that finally removes unused columns in the geo_node_status table.
* Added SiteStatistics as counter cache for Projects and WikisGabriel Mazetto2018-07-241-0/+42
|
* Updates from `rubocop -a`Lin Jen-Shin2018-07-091-1/+1
|
* Replace '.team << [user, role]' with 'add_role(user)' in specs36782-replace-team-user-role-with-add_role-user-in-specsblackst0ne2017-12-221-1/+1
|
* Change all `:empty_project` to `:project`rs-empty_project-defaultRobert Speicher2017-08-021-2/+2
|
* Refactor Project.with_feature_available_for_userYorick Peterse2017-06-161-0/+12
| | | | | | | | | | | This method used to use a UNION, which would lead to it performing the same query twice; producing less than ideal performance. Further, in certain cases ActiveRecord could get confused and mess up the variable bindings, though it's not clear how/why exactly this happens. Fortunately we can work around all of this by building some of the WHERE conditions manually, allowing us to use a simple OR statement to get all the data we want without any of the above problems.
* Add traits for ProjectFeatures to Project factorySemyon Pupkov2017-02-051-2/+0
| | | | https://gitlab.com/gitlab-org/gitlab-ce/issues/24007
* Use `:empty_project` where possible in model specsrs-empty_project-modelsRobert Speicher2017-01-261-2/+2
|
* Add visibility level to project repositoryissue_19734_2Felipe Artur2016-10-171-1/+22
|
* Project tools visibility levelFelipe Artur2016-09-011-0/+91