Manoj M J authored 5 years ago and Ash McKenzie committed 5 years ago

This change implements Application
Statistics API

(cherry picked from commit 0bf7fecdee5a200eeb4f27b4888a57ceee63bde9)

Etienne Baqué authored 5 years ago and Andreas Brandl committed 5 years ago

Modified schema via migrations.
Added one-to-one relationship between the two models.
Added changelog file

Instead of sending varied data to Gitaly, and making Gitaly construct
various messages, build the messages first and have Gitaly print
either basic messages or alert messages, in the order they come.

Depends on https://gitlab.com/gitlab-org/gitaly/merge_requests/1410

(cherry picked from commit 897a9d308db46b620b738b98f2b0e5630ac7d2dd)

User images and videos will get proxied through
the Camo server in order to keep malicious
sites from collecting the IP address of users.

In GitLab 9.0,
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9661 removed the
`subscribed` flag from the API when the user requested a list of issues
or merge requests since calculating this value triggers extensive
Markdown processing.

In GitLab 12.0 via a4fbf39e, we accidentally reintroduced this
performance regression by changing `IssueBasic` to `Issue` in
`entities.rb`. This showed up as a Gitaly N+1 issue since the Markdown
processing would attempt to extract a commit if it detected a regex that
matched a commit.

We restore the prior behavior by once again removing the `subscribed`
flag for the bulk list of issues and merge requests and add a test to
ensure they aren't reintroduced.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66202

As decided in https://gitlab.com/gitlab-org/gitlab-ce/issues/53593

These counts significantly increase the load time for these
requests. Users can now opt in to receiving the counts by setting
`with_counts=true` in requests. This is a breaking change, but hopefully
a fairly minor one.

Expose time since starring on project/:id/starrers API endpoint; exclude private profiles here as well

`allow_local_requests_for_hooks_and_services` was renamed to
`allow_local_requests_for_web_hooks_and_services`.

These are not required because MySQL is not
supported anymore

None of this code can be reached any more, so it can all be removed

Imre (Admin) authored 5 years ago and James Lopez committed 5 years ago

EE MR: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14598

This is basically a copy of the API for project clusters.

The auto_devops object sometimes doesn't exists. We may need to create
it.

We map the boolean to the string 'fetch' or 'clone', to be more
explicit.

- issues_access_level
- repository_access_level
- merge_requests_access_level
- builds_access_level
- wiki_access_level
- snippets_access_level

Jason Goodman authored 5 years ago and Nick Thomas committed 5 years ago

Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at

- Add test for N+1 queries
- Add destroyable lists scope to Board and List
- Preload lists for both project and group boards

This couples the code that transitions the `MergeRequest#merge_status`
and refs/merge-requests/:iid/merge ref update.

In general, instead of directly telling `MergeToRefService` to update
the merge ref, we should rely on `MergeabilityCheckService` to keep
both the merge status and merge ref synced. Now, if the merge_status is
`can_be_merged` it means the merge-ref is also updated to the latest.

We've also updated the logic to be more systematic and less user-based.

Count issues related merge requests based on user access level. And
issue can have related MRs from projects where user does not have
access so the number of related merge requests should be adjusted
based on user's ability to access the related MRs.

https://gitlab.com/gitlab-org/gitlab-ce/issues/59581