delta/gitlab/gitlab-ce.git/spec/requests, branch docs/single-codebase-dev-guides

#46469 - Added ref querystring parameter to project search to allow searching on branches other than master

2019-05-17T06:10:08+00:00

Add correlation id to all sentry errors

2019-05-13T18:27:41+00:00

Before this, we were only adding the correlation id to the "acceptable
exceptions" which we handle in code.

But we need to add it to the default raven context so the information
would be available for uncaught exceptions.

Merge branch '58404-set-default-max-depth-for-GraphQL' into 'master'

2019-05-08T08:46:56+00:00

58404 - setup max depth for graphql

Closes #58404

See merge request gitlab-org/gitlab-ce!25737

Confirm existence of head_pipeline if pipeline success required

2019-05-07T16:06:53+00:00

Pipelines are created by an async worker, so a rapid sequence of API
calls can trigger a state where the pipeline, whose existence is part of
determining if we wait for the pipeline to successfully complete before
merging, can trigger the MR to be immediately merged instead.

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

Add improvements to the global search process

2019-05-07T11:08:25+00:00

Removed the conditions added to
Project.with_feature_available_for_user, and moved to the
IssuableFinder. Now, we ensure that, in the projects retrieved
in the Finder, the user has enough access for the feature.

Allow replying to an individual note in the API

2019-05-06T18:48:32+00:00

If you can do this in the UI, you should be able to do it in the API. If
a discussion is not a single note discussion, or it is replyable, you
can reply to it.

58404 - setup max depth for graphql

2019-05-06T15:02:29+00:00

58404 - add change log


58404 - add spec


58404 - add more spec to test depth 2


58404 - fix spec


58404 - fix rubocop


58404 - refactor the code by Bob's advice


58404 - revert changes of all_graphql_fields_for


58404 - change text only


58404 - fix rspec according to gitlab's standard


58404 - revert previous spec


58404 - fix rubocop

Implement support for CI variables of type file

2019-05-06T13:11:42+00:00

Add env_var and file as supported types for CI variables. Variables of
type file expose to users existing gitlab-runner behaviour - save
variable value into a temp file and set the path to this file in an ENV
var named after the variable key.

Resolves https://gitlab.com/gitlab-org/gitlab-ce/issues/46806.

Allow guests users to access project releases

2019-05-03T13:29:20+00:00

This is step one of resolving
https://gitlab.com/gitlab-org/gitlab-ce/issues/56838.

Here is what changed:
- Revert the security fix from bdee9e8412d.
- Do not leak repository information (tag name, commit) to guests in API
responses.
- Do not include links to source code in API responses for users that do
not have download_code access.
- Show Releases in sidebar for guests.
- Do not display links to source code under Assets for users that do not
have download_code access.

GET ':id/releases/:tag_name' still do not allow guests to access
releases. This is to prevent guessing tag existence.

Whitelist query limits for internal API

2019-05-03T04:02:15+00:00

When creating a merge request for push options, there may be over 100
queries that are run to create a merge request. Even after we reduce the
number of queries by disabling the Sidekiq jobs, it appears we still
hover near this limit.

Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/11450