summaryrefslogtreecommitdiff
path: root/spec/finders
Commit message (Collapse)AuthorAgeFilesLines
* [CE] Reduce differences with EE in users_finder_spec.rbRémy Coutable2019-03-212-18/+15
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* [CE] Reduce differences with EE in snippets_finder_spec.rbRémy Coutable2019-03-211-127/+94
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* [CE] Reduce differences with EE in merge_requests_finder_spec.rbRémy Coutable2019-03-211-93/+44
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* [CE] Reduce differences with EE in issues_finder_spec.rbRémy Coutable2019-03-211-37/+43
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* [CE] Reduce differences with EE in group_projects_finder_spec.rbRémy Coutable2019-03-211-20/+19
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Merge branch 'only-counted-active-milestones-as-started' into 'master'Kamil Trzciński2019-03-191-0/+3
|\ | | | | | | | | | | | | Only count active milestones as started Closes #58782 See merge request gitlab-org/gitlab-ce!25969
| * Only count active milestones as startedSean McGivern2019-03-191-0/+3
| | | | | | | | | | The Upcoming milestone filter only considers active milestones, but the Started one included closed milestones, too. This was inconsistent.
* | Allow filtering labels by a single characterSean McGivern2019-03-131-0/+6
|/ | | | | | | | | | | | When we use Gitlab::SQL::Pattern, this typically relates to a trigram index. As the 'tri' indicates, we need at least three characters to be able to use that index. Labels don't have a trigram index, because we never allow you to search for them globally: it's always in the context of a project or a group. In that context, it's just as fast to search for a single character (in general) because there is already a pretty specific index being used.
* Filter merge requests by target branchHiroyuki Sato2019-03-091-1/+1
|
* Display the correct number of MRs a user has access toIgor Drozdov2019-03-051-199/+309
|
* Merge dev master into GitLab.com masterYorick Peterse2019-03-041-1/+25
|\
| * Merge branch 'security-commit-private-related-mr' into 'master'Yorick Peterse2019-03-041-1/+25
| |\ | | | | | | | | | | | | | | | | | | Don't allow non-members to see private related MRs Closes #2787 See merge request gitlab/gitlabhq!2866
| | * Modify MergeRequestsFinder to allow filtering by commitPatrick Bajao2019-01-281-1/+25
| | |
| | * Merge branch 'security-guests-can-see-list-of-merge-requests' into 'master'Yorick Peterse2019-01-251-9/+23
| | |\ | | | | | | | | | | | | | | | | [master] Group Guests are no longer able to see merge requests See merge request gitlab/gitlabhq!2694
| | | * Group Guests are no longer able to see merge requestsTiago Botelho2019-01-211-9/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Group guests will only be displayed merge requests to projects they have a access level to, higher than Reporter. Visible projects will still display the merge requests to Guests
| | * | Merge branch 'security-contributed-projects' into 'master'Yorick Peterse2019-01-251-0/+12
| | |\ \ | | | |/ | | |/| | | | | | | | | [master] Fix contributed projects info is still visible even user enable private profile See merge request gitlab/gitlabhq!2743
| | | * Fix contributed projects finder shown private infoJames Lopez2019-01-081-0/+12
| | | |
* | | | Merge branch '54643-lower_issuable_finder_complexity' into 'master'Sean McGivern2019-03-011-30/+25
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | IssuableFinder - Always use CTE for group counts Closes #54643 See merge request gitlab-org/gitlab-ce!25411
| * | | | Always use CTE for IssuableFinder countsMario de la Ossa2019-02-281-30/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the CTE is faster than a subquery and the only reason we're using a subquery is that the CTE can't handle sorting by certain attributes, let's use the CTE always (when the feature flag is enabled) when counting, since we can ignore ordering if we just want a count of results.
* | | | | make assertions on objects instead of tag namesAlexis Reigel2019-02-271-12/+12
| | | | |
* | | | | don't filter tags by taggable typeAlexis Reigel2019-02-271-15/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to performance reasons we cannot use the type filter on the tags. The table for ActsAsTaggableOn is too big and too unoptimized, such that the queries time out on production. See the discussion https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19740#note_120087938 for more info.
* | | | | use lazy ajax filter dropdown for runner tagsAlexis Reigel2019-02-271-0/+66
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the potential number of available runner tags is too large to load it statically to a dropdown. we use the same lazy loaded dropdown as is used for the users dropdown already.
* | | | | add tag filter to admin runners pageAlexis Reigel2019-02-271-0/+8
| |/ / / |/| | |
* | | | Merge branch 'filter-confidential-issues' into 'master'Kamil Trzciński2019-02-261-1/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Ability to filter confidential issues Closes #50747 See merge request gitlab-org/gitlab-ce!24960
* | | | Revert "Merge branch 'filter-confidential-issues' into 'master'"Michael Kozono2019-02-251-27/+1
| | | | | | | | | | | | | | | | | | | | This reverts commit d133bf84c668df3dfc9938bb04150754cb873c8b, reversing changes made to 7981c0292b07a0138b096fa082341fcb13e9ce2b.
* | | | Merge branch 'filter-confidential-issues' into 'master'Kamil Trzciński2019-02-251-1/+27
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ability to filter confidential issues Closes #50747 See merge request gitlab-org/gitlab-ce!24960
| * | | | Only use boolean parameters internallyRobert Schilling2019-02-221-2/+2
| | | | | | | | | | | | | | | | | | | | Use internally only boolean params.
| * | | | Add specs for filtering confidential issuesRobert Schilling2019-02-211-1/+27
| | | | |
* | | | | Merge branch ↵Robert Speicher2019-02-211-0/+30
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | '56492-implement-new-arguments-state-closed_before-and-closed_after-for-issuesresolver-in-graphql' into 'master' Implement new arguments `state`, `closed_before` and `closed_after` for `IssuesResolver` in GraphQL Closes #56492 See merge request gitlab-org/gitlab-ce!24910
| * | | | Allow IssuableFinder to filter by closed_atRémy Coutable2019-02-211-0/+30
| |/ / / | | | | | | | | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* | | | Ignore ordering when calling find_by on findersSean McGivern2019-02-201-1/+21
|/ / / | | | | | | | | | | | | | | | | | | We shouldn't care about the ordering here; if we did, it would be more appropriate to use `take` or `first`. Having the ordering can result in the database picking a bad query plan, as it might think sorting the whole table first is the best option.
* | | Merge branch 'search-title' into 'master'Sean McGivern2019-02-051-0/+8
|\ \ \ | | | | | | | | | | | | | | | | Add 'in' filter that modifies scope of 'search' filter to issues and merge requests API See merge request gitlab-org/gitlab-ce!24350
| * | | Add 'in' filter that modifies scope of 'search' filter to issues and merge ↵Hiroyuki Sato2019-01-141-0/+8
| |/ / | | | | | | | | | requests API
* | | Group Guests are no longer able to see merge requestsTiago Botelho2019-01-311-9/+23
| | | | | | | | | | | | | | | | | | | | | Group guests will only be displayed merge requests to projects they have a access level to, higher than Reporter. Visible projects will still display the merge requests to Guests
* | | Fix contributed projects finder shown private infoJames Lopez2019-01-311-0/+12
| | |
* | | Merge branch '54905-milestone-search' into 'master'Sean McGivern2019-01-251-0/+6
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Resolve "Milestone search" Closes #54905 See merge request gitlab-org/gitlab-ce!24265
| * | | Adds milestone searchJacopo2019-01-241-0/+6
| |/ / | | | | | | | | | | | | | | | | | | Adds to search ILIKE search for milestones title in: - Milestones dashboard - Group milestones page - Project milestones page
* | | Enable the Layout/ExtraSpacing cop56392-enable-the-layout-extraspacing-copRémy Coutable2019-01-245-14/+14
|/ / | | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* | Merge branch '53431-fix-upcoming-milestone-filter-for-groups' into 'master'Sean McGivern2019-01-111-7/+12
|\ \ | | | | | | | | | | | | | | | | | | Add group milestones in upcoming filter Closes #53431 See merge request gitlab-org/gitlab-ce!23098
| * | Add group milestones in upcoming filterHeinrich Lee Yu2018-12-311-7/+12
| | |
* | | Initial Serverless Functions detailed viewChris Baumbauer2019-01-101-3/+22
| |/ |/|
* | ReleasesFinder will always return a relationAlessio Caiazza2018-12-311-5/+4
| |
* | Add releases APIAlessio Caiazza2018-12-311-0/+43
|/ | | | | | | | | | | This commit introduces Releases API under /api/v4/projects/:id/releases * We are introducing release policies at project level. * We are deprecating releases changes from tags, both api and web interface. * Tags::CreateService no longer create a release This feature is controlled by :releases_page feature flag
* Hide confidential events in rubyBob Van Landuyt2018-12-173-1/+35
| | | | | | | | | | | | We're filtering the events using `Event#visible_to_user?`. At most we're loading 100 events at once. Pagination is also dealt with in the finder, but the resulting array is wrapped in a `Kaminari.paginate_array` so the API's pagination helpers keep working. We're passing the total count into that paginatable array, which would include confidential events. But we're not disclosing anything.
* Check can :read_clusters in finderThong Kuah2018-12-171-0/+16
| | | | | This is in addtion to the can checks we have in the controller, as a finder can be used elsewhere in the future.
* Show clusters of ancestors in cluster list pageThong Kuah2018-12-171-0/+61
| | | | | Show both the cluster(s) of the clusterable, and the cluster(s) of ancestor groups.
* Merge branch 'move-group-issues-search-cte-up-the-chain' into 'master'Douwe Maan2018-12-071-0/+127
|\ | | | | | | | | Add a flag to use a subquery for group issues search See merge request gitlab-org/gitlab-ce!23445
| * Add a flag to use a subquery for group issues searchSean McGivern2018-11-301-0/+127
| | | | | | | | | | | | | | | | | | | | We already had a flag to use a CTE, but this broke searching in some cases where we need to sort by a joined table. Disabling the CTE flag makes searches much slower. The new flag, to use a subquery, makes them slightly slower than the CTE, while maintaining correctness. If both it and the CTE flag are enabled, the subquery takes precedence.
* | Introduce Knative Serverless TabDylan Griffith2018-12-061-0/+60
| |
* | Resolve "Can add an existing group member into a group project with new ↵James Lopez2018-12-061-1/+1
|/ | | | permissions but permissions are not overridden"
View Lorry Controller Status