| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | 2020-06-18 | 2 | -2/+2 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-04-01 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-06 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-18 | 1 | -0/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-16 | 2 | -0/+4 |
| | | |||||
| * | Ignore ordering when calling find_by on finders | Sean McGivern | 2019-02-20 | 1 | -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. | ||||
| * | Hide confidential events in ruby | Bob Van Landuyt | 2018-12-17 | 1 | -0/+16 |
| | | | | | | | | | | | | | 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. | ||||
| * | Resolve "Rename the `Master` role to `Maintainer`" Backend | Mark Chao | 2018-07-11 | 1 | -1/+1 |
| | | |||||
| * | Port `read_cross_project` ability from EE | Bob Van Landuyt | 2018-02-22 | 2 | -0/+188 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |