| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
Expose whether current user can push into a branch on branches API
See merge request gitlab-org/gitlab-ce!19958
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Fix group pagination and add sort by id to groups and subgroups
Closes #47409
See merge request gitlab-org/gitlab-ce!19665
|
| |
| |
| |
| |
| |
| |
| |
| | |
Adding primary key to database query order rule
generates deterministic sort result and thus pagination.
This is needed because subgroups can have identical names.
Signed-off-by: Marko, Peter <peter.marko@siemens.com>
|
| |
| |
| |
| |
| |
| |
| | |
With introduction of subgroups, many groups may have the same
name and/or path, thus further sorting options are necessary.
Signed-off-by: Marko, Peter <peter.marko@siemens.com>
|
| |
| |
| |
| |
| |
| | |
We have long polling mechanism which is not being used by paused runners.
This makes the paused runner to generate a request every 3s,
where it could be fired only every 1h.
|
| | |
|
| |
| |
| |
| | |
ActionController::Parameters no longer returns an hash in Rails 5
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Resolve "Regressions for assigning group milestone from ancestor"
Closes #47735
See merge request gitlab-org/gitlab-ce!19721
|
| |/ |
|
| | |
|
|\ \
| |/
|/|
| |
| | |
Added with_stats option to GET /projects/:id/repository/commits (API)
See merge request gitlab-org/gitlab-ce!19484
|
| | |
|
| | |
|
|/ |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Add Avatar API
Closes #45821
See merge request gitlab-org/gitlab-ce!19121
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Resolve "POST api/v4/projects/:id/pipeline should accept variables"
Closes #25045
See merge request gitlab-org/gitlab-ce!19124
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Eliminate N+1 queries with authors and push_data_payload in Events API
See merge request gitlab-org/gitlab-ce!19347
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Rephrase Merge Request Maintainer Edit
See merge request gitlab-org/gitlab-ce!19061
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
branch"
"Maintainer" will be freed to be used for #42751
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Eliminate N+1 queries for CI job artifacts in /api/projects/:id/pipelines/:pipeline_id/jobs
See merge request gitlab-org/gitlab-ce!19353
|
| | | |
| | | |
| | | |
| | | | |
/api/projects/:id/pipelines/:pipeline_id/jobs
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was being masked by the statement cache because only one author was used
per issue in the test..
Also adds support for an Rspec matcher `exceed_all_query_limit`.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Support presigned multipart uploads
See merge request gitlab-org/gitlab-ce!18855
|
| | | | | |
|
|\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Remove N+1 query for author in issues API
See merge request gitlab-org/gitlab-ce!19345
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was being masked by the statement cache because only one author was used
per issue in the test..
Also adds support for an Rspec matcher `exceed_all_query_limit`.
|
| |/ /
|/| | |
|
|/ /
| |
| |
| |
| | |
Now that we are checking `MergeRequest#for_fork?`, we also need
the source project preloaded for a merge request.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
'master'
Improve validations for Ci::Runner#runner_type
See merge request gitlab-org/gitlab-ce!18901
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| | |
Eliminate cached N+1 queries for projects in Issue API
See merge request gitlab-org/gitlab-ce!19269
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In CE, every `Issue` entity is also a `ProjectEntity`, which calls
`entity&.project.try(:id)` to show the project ID. In an API
request with 100 issues, this would hit the Rails statement cache 100 times
for the same project and cause unnecessary overhead as related models would
also be loaded.
In EE, we call `Issue#supports_weight?` for each issue, which then calls
`project&.feature_available?(:issue_weights)`. If the project is not
preloaded, this incurs additional overhead, as each individual Project
object has to be queried. This can lead to a significant performance hit.
In loading the CE project with 100 issues, this contributed to at least 22%
of the load time.
See https://gitlab.com/gitlab-org/gitlab-ce/issues/47031 for why testing this
is a bit tricky.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Removal of API v3 from the codebase
Closes #36819
See merge request gitlab-org/gitlab-ce!18970
|
| | |
|
|/
|
|
| |
Identified while resolving conflicts in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5906
|
|\
| |
| |
| |
| | |
Only preload member records for the relevant projects/groups/user in projects API
See merge request gitlab-org/gitlab-ce!18945
|
| |
| |
| |
| | |
projects API
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Replace grape-route-helpers with our own grape-path-helpers
Closes #45718
See merge request gitlab-org/gitlab-ce!19240
|