summaryrefslogtreecommitdiff
path: root/spec/requests/api
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' of dev.gitlab.org:gitlab/gitlabhqRobert Speicher2019-07-291-28/+0
|\
| * Merge branch 'security-remove-take-trigger-ownership-feature' into 'master'GitLab Release Tools Bot2019-07-261-28/+0
| |\ | | | | | | | | | | | | | | | | | | Drop feature to take ownership of a trigger token Closes #2868 See merge request gitlab/gitlabhq!3198
| | * Drop feature to take ownership of a trigger tokenFabio Pitino2019-07-101-28/+0
| | | | | | | | | | | | | | | | | | | | | Removing API and frontend interactions that allowed users to take ownership of a trigger token. Removed mentions from the documentation.
* | | Merge branch 'add-git-blame-api' into 'master'Nick Thomas2019-07-291-0/+162
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Expose git blame in api Closes #51345 See merge request gitlab-org/gitlab-ce!30675
| * | | Add git blame apiOleg Zubchenko2019-07-261-0/+162
| | | |
* | | | Merge branch 'rs-resource-label-events-api' into 'master'Lin Jen-Shin2019-07-261-44/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Extract resource_label_events API shared examples See merge request gitlab-org/gitlab-ce!31156
| * | | | Simplify resource_label_events API shared examplers-resource-label-events-apiRobert Speicher2019-07-251-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | We don't need a repository, and we only need a private user in one example, so we can scope it locally there.
| * | | | Extract resource_label_events API shared examplesRobert Speicher2019-07-251-42/+0
| | |/ / | |/| | | | | | | | | | This will allow us to reuse them in an EE-only spec.
* | | | Remove code related to object hierarchy in MySQLremove-nested-groups-checksHeinrich Lee Yu2019-07-258-15/+15
|/ / / | | | | | | | | | | | | These are not required because MySQL is not supported anymore
* | | Merge branch 'gsemet/gitlab-ce-gsemet-master-patch-33258' into 'master'Sean McGivern2019-07-231-4/+20
|\ \ \ | | | | | | | | | | | | | | | | Multiple pipeline support for Build status See merge request gitlab-org/gitlab-ce!30828
| * | | Add specs for specifying pipeline behaviorMatija Čupić2019-07-231-4/+20
| | | | | | | | | | | | | | | | | | | | Adds specs for testing the new behavior of specifying a pipeline when POSTing a status.
* | | | Make subgroup_creation_level default to maintainer at SQL levelFabio Papa2019-07-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | - Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
* | | | Style rules; Revert some examplesFabio Papa2019-07-191-2/+2
| | | |
* | | | Make subgroup_creation_level default to maintainer at SQL levelFabio Papa2019-07-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | - Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
* | | | Style rules; Revert some examplesFabio Papa2019-07-191-2/+2
| | | |
* | | | Make subgroup_creation_level default to maintainer at SQL levelFabio Papa2019-07-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | - Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
* | | | Style rules; Revert some examplesFabio Papa2019-07-191-2/+2
| | | |
* | | | Make subgroup_creation_level default to maintainer at SQL levelFabio Papa2019-07-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | - Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
* | | | Style rules; Revert some examplesFabio Papa2019-07-191-2/+2
| | | |
* | | | Make subgroup_creation_level default to maintainer at SQL levelFabio Papa2019-07-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | - Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
* | | | Style rules; Revert some examplesFabio Papa2019-07-191-2/+2
| | | |
* | | | Make subgroup_creation_level default to maintainer at SQL levelFabio Papa2019-07-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | - Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
* | | | Style rules; Revert some examplesFabio Papa2019-07-191-2/+2
| | | |
* | | | Modify API spec to expect a maintainer to be able to create subgroupFabio Papa2019-07-191-2/+2
| | | |
* | | | Merge branch 'webide-commit-use-correct-parent' into 'master'Nick Thomas2019-07-181-45/+158
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Use correct parent when committing in WebIDE See merge request gitlab-org/gitlab-ce!29598
| * | | | Add start_sha to commits APIMarkus Koller2019-07-181-45/+158
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When passing start_branch on committing from the WebIDE, it's possible that the branch has changed since editing started, which results in the change being applied on top of the latest commit in the branch and overwriting the new changes. By passing the start_sha instead we can make sure that the change is applied on top of the commit which the user started editing from.
* | | | Refactor RedisCounter and WebIdeCommitsCounterFrancisco Javier López2019-07-171-1/+1
|/ / / | | | | | | | | | | | | This MR refactor RedisCounter and WebIdeCommitsCounter to be reused by other components.
* | | CE port of "Move external authorization service API management to EE"Imre Farkas2019-07-171-49/+0
| | | | | | | | | | | | EE MR: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14598
* | | Merge branch '12800-read-and-write-user-admin-notes-via-api-ce' into 'master'Stan Hu2019-07-161-0/+8
|\ \ \ | | | | | | | | | | | | | | | | CE Backport: Read and write User "Admin notes" via API See merge request gitlab-org/gitlab-ce!30775
| * | | CE: Read and write User "Admin notes" via APImanojmj2019-07-171-0/+8
| | |/ | |/| | | | | | | | | | | | | This change adds the ability to read and write admin notes for a user via the USER API
* | | Refactored WebIdeCommitsCount classFrancisco Javier López2019-07-161-1/+1
| | | | | | | | | | | | | | | | | | We're adding more redis base counters to the web ide and other classes. We're refactoring this class in other to use the logic in other places.
* | | Simplify factories for servicesJarka Košanová2019-07-161-3/+10
| | | | | | | | | | | | | | | | | | - use predefined factories when creating projects with services - remove unnecessary arguments
* | | Cleanup usages of `JSON.parse` in specsPeter Leitzen2019-07-161-2/+2
| | | | | | | | | | | | Prefer `json_response` where applicable.
* | | Migrate null values for users.private_profileAdam Hegyi2019-07-151-0/+8
| |/ |/| | | | | | | - Background migration for changing null values to false - Set false as default value for private_profile DB column
* | Merge branch 'bvl-rename-routes-after-user-rename' into 'master'Jan Provaznik2019-07-121-6/+6
|\ \ | | | | | | | | | | | | Set the name of a user-namespace to the user name See merge request gitlab-org/gitlab-ce!23272
| * | Use namespace#path for building urls in specsBob Van Landuyt2019-07-091-6/+6
| | | | | | | | | | | | | | | | | | Some of the specs were using namespace names instead of paths for building URLS. This would fail since we now build a namespace with a user's name instead of a user's username.
* | | Merge branch '55623-group-cluster-apis' into 'master'Grzegorz Bizon2019-07-122-3/+465
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | Resolve "API support for group-level clusters" Closes #55623 See merge request gitlab-org/gitlab-ce!30213
| * | Add API for CRUD group clusters55623-group-cluster-apisDylan Griffith2019-07-111-0/+452
| | | | | | | | | | | | This is basically a copy of the API for project clusters.
| * | Refactor: model errors for multi cluster validationDylan Griffith2019-07-111-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current approach requires catching exceptions to handle these errors and callers are already handling model validations so it seems more appropriate. Also it seemed to convoluted to add this logic directly to the model since the model needs to check too many possible associations to determine whether or not there are more than one cluster since the model doesn't know what it's being created on. Additionally we only wanted to validate during create to avoid the risk of existing models becoming invalid by many different edge cases.
* | | GraphQL support for Notes created in discussions62826-graphql-note-mutationsLuke Duncalfe2019-07-101-1/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A new `discussion_id` argument on the `createNote` mutation allows people to create a note within that discussion. The ability to lazy-load Discussions has been added, so GraphQL.object_from_id can treat Discussions the same as AR objects and batch load them. https://gitlab.com/gitlab-org/gitlab-ce/issues/62826 https://gitlab.com/gitlab-org/gitlab-ee/issues/9489
* | | GraphQL mutations for managing NotesLuke Duncalfe2019-07-105-0/+301
| | | | | | | | | | | | https://gitlab.com/gitlab-org/gitlab-ce/issues/62826
* | | Merge branch 'master' into sathieu/gitlab-ce-project_apiDouglas Barbosa Alexandre2019-07-095-11/+129
|\ \ \ | | |/ | |/|
| * | Remove `:graphql` feature flagcharlie ablett2019-07-091-10/+0
| | | | | | | | | | | | | | | | | | | | | | | | - Remove `FeatureConstrainer` call wrapping api endpoint - Remove `Feature.enabled?(:graphql)` conditionals in back and frontend - Modify graphql test to be graphql flag agnostic - Remove api routing spec - Remove frontend feature flag via `gon`
| * | Updates on success of an MR the count on top and in other tabsTim Zallmann2019-07-091-0/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New API endpoint for merge request count Updates all open tabs at the same time with one call Restructured API response API response changed to 401 if no current_user Added API + JS specs Fix for Static Check Updated Count on Open/Close, Assign/Unassign of MR's Checking if MR Count is refreshed Added # frozen_string_literal: true to spec Added Changelog
| * | Adding order by to list runner jobs api.sujay patel2019-07-051-0/+44
| | |
| * | Merge branch ↵Bob Van Landuyt2019-07-051-0/+31
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | '58409-increase-graphql-complexity-for-fields-that-make-gitaly-calls' into 'master' Increase GraphQL complexity for fields that make Gitaly Calls Closes #58409 See merge request gitlab-org/gitlab-ce!28814
| | * | Address reviewer commentscharlieablett2019-07-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | - Add 1 for all fields that call Gitaly (with resolvers or without) - Clarify comment regarding Gitaly call alert - Expose predicate `calls_gitaly?` instead of ivar
| | * | Alert if `calls_gitaly` declaration missingcharlieablett2019-07-031-0/+31
| | |/ | | | | | | | | | | | | | | | | | | - Move `calls_gitaly_check` to public - Add instrumentation for flagging missing CallsGitaly declarations - Wrap resolver proc in before-and-after Gitaly counts to get the net Gitaly call count for the resolver.
| * | Allow asynchronous rebase operations to be monitoredNick Thomas2019-07-041-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | This MR introduces tracking of the `rebase_jid` for merge requests. As with `merge_ongoing?`, `rebase_in_progress?` will now return true if a rebase is proceeding in sidekiq. After one release, we should remove the Gitaly-based lookup of rebases. It is much better to track this kind of thing via the database.
| * | Merge branch 'sh-fix-issue-63349' into 'master'Rémy Coutable2019-07-041-1/+1
| |\ \ | | |/ | |/| | | | | | | | | | | | | Make Housekeeping button do a full garbage collection Closes #63349 See merge request gitlab-org/gitlab-ce!30289
View Lorry Controller Status