| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| | |
Protected Tags
Closes #18471
See merge request !10356
|
| |\
| | |
| | |
| | | |
# Conflicts:
# spec/lib/gitlab/import_export/all_models.yml
|
| |\ \ |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
# Conflicts:
# app/assets/javascripts/dispatcher.js
# app/assets/stylesheets/pages/projects.scss
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |_|_|/
|/| | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
adds initial microsoft teams integration
See merge request !10412
|
| | | | | |
|
| |_|_|/
|/| | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
ProjectsFinder should handle more options
Closes #28810
See merge request !9682
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Extended ProjectFinder in order to handle the following options:
- current_user - which user use
- project_ids_relation: int[] - project ids to use
- params:
- trending: boolean
- non_public: boolean
- starred: boolean
- sort: string
- visibility_level: int
- tags: string[]
- personal: boolean
- search: string
- non_archived: boolean
GroupProjectsFinder now inherits from ProjectsFinder.
Changed the code in order to use the new available options.
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
Enable creation of deploy keys with write access via the API
Closes #30021
See merge request !10488
|
| | | |
| | | |
| | | |
| | | | |
* Documentation was incorrectly advertising the missing param
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add "search" optional param and docs for V4
Closes #30195
See merge request !10358
|
| |/ / /
| | | |
| | | |
| | | | |
Notice that this param is being supported since V3, but we have not added the proper docs for it
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Implement Gitaly refs client
See merge request !9291
|
| | | | |
|
| |/ /
|/| | |
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Fixes milestone/merge_request API endpoint to really scope the results
See merge request !10369
|
| | |
| | |
| | |
| | |
| | | |
The MergeRequestsFinder uses the milestone_title instead of the
milestone_id
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Backport API changes needed to fix sticking in EE
See merge request !10376
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
These changes are ported over from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1502 to reduce
the number of merge conflicts that may occur.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Enable Style/Proc cop for rubocop
See merge request !10382
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
#22303 fix mode representation git::tree ( in base 8 )
Closes #22303
See merge request !9780
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Introduce "polling_interval_multiplier" as application setting
Closes #29759
See merge request !10280
|
| |/ /
| | |
| | |
| | |
| | | |
Implement module for setting "Poll-Interval" response header.
Return 429 in ETag caching middleware when polling is disabled.
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
One Gitaly connection per storage shard
See merge request !10150
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix API group/issues default state filter
Closes #23655
See merge request !10253
|
| | | | |
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
API: Make the /notes endpoint work with noteable iid instead of id
Closes #29871
See merge request !10258
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In API V4 all endpoints were changed so Merge Requests and Issues
should be referred by iid, instead of id. Except the /notes endpoint
was forgotten. So change the endpoints from:
- /projects/:id/issues/:issue_id/notes
- /projects/:id/merge_requests/:merge_request_id/notes
To:
- /projects/:id/issues/:issue_iid/notes
- /projects/:id/merge_requests/:merge_request_iid/notes
For Project Snippets nothing changes.
|
| |/ /
| | |
| | |
| | | |
Comments for a merge request should be obtained to the `notes` endpoint.
|
|/ / |
|
|/
|
|
| |
Closes #29631
|
|\
| |
| |
| |
| | |
Fix regressions introduced while adding CI endpoints in API v4
See merge request !9952
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In APIv1 we've been sending all jobs from previous stages and
a `dependencies` list with names of jobs that user want to download
artifacts from. This was selected on Runners side.
In APIv1 we've planned to send only jobs that were defined (if any; and
all previous jobs by default). However I've missed the fact that
it was Runner who selected jobs, not GitLab. And now current version
of APIV4 sends all jobs everytime.
This commit fixes this. If user will define `dependencies` in his job,
then GitLab will send only selected jobs.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Artifacts download for authorization is using a job token of job to
which the artifact belongs. In APIv1 the token was sent with dependent
jobs details and in APIv4 it was designed to also contain it.
However I forgot about this parameter while working on
`/api/v4/jobs/request` endpoint.
This commit adds a missing parameter which is required for APIv4 to work
properly.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In Runner v1.3.0 we've started to send User-Agent header with Runner's
version data. Since GitLab v8.12.0 we've started to use this header to check
if used Runner's version supports 204 status code instead of 404 as a
response when there is no jobs to execute by a Runner.
In APIv4 (introduced in GitLab 9.0.0) will require Runner v9.0.0. And
writing more accurately: GitLab Runner v9.0.0 will require GitLab at
least 9.0.0. Because of such breaking change we are able to switch
entirely to 204 response code and there is no need to do check of
User-Agent.
This commit removes useless code and complexity.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In APIv1 we were using UpdateJob to verify if the runner exists. It was
the only method that was using Runner's token and used in special way
had no side effects (like scheduling a new job or unregisterring a
Runner).
In APIv4 we've change UpdateJob to use job's token as authentication
credentials, and that way we've removed the only endpoint that could
be used to verify if the Runner with a certain token exists in target
GitLab installation.
This commit adds `POST /api/v4/runners/verify` endpoint whose only
responsibility is to respond if Runner with posted credentials exists or
not.
|
| | |
|
|/
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|