GitLab

GitLab's query for labels now only returns counts if `with_counts=true`
is added, e.g. `GET /projects/:id/labels?with_counts=true`.

45a2205d test/types: add tests for the data models
92368eb5 data: Add some data for the discussions test from a MR
df2e51d2 data/fetch: add an option to dump the whole content of a query
a245bf17 gitlab: Add a couple of methods to get and create discussions on MRs
8f406421

 types: Add the necessary models to fetch discussion information
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !158

Since there are multiple different cases with some model differences
between them, we need more than just one example of discussion, hence
the full dump

The default code only take the first item when a query returns an
array, but in some cases we want more data than that, for instance in
the coming discussion tests.

It means extending a little bit the Note model, as well as creating the
Discussion model itself, which is quite basic.

7b4918de

 test: update data for gitlab 12.2
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !162

9276e510

 gitlab: fix query parameters for adding a user to a project
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !160

Fixes: #20

f8c93940 types: update for 12.1
b8d338af types: Organize project feature-enabled fields
51d75852 test: Update sample project data
b76345d0

 test: Update sample issue data
Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !156

Projects gained fields for visibility of individual features.

They also gained fields for devops and build configuration.
Leave out bindings for these for now.

The live Gitlab project from which we fetch sample data has been
updated.  Update our sample and expected results accordingly.

In order to generate data for commit e0312dcf (types: Add resource label
events, 2019-07-16, v0.1200.1~1^2~1) a label was added to our sample
issue.  Fetch updated data for the issue and revise expected values.

53f8d3db cargo: explicitly enable serde derive feature
3c72fb20

 cargo: drop unused dependency on serde_derive
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !157

Previously it was enabled only by one of our other dependencies.
Enable it explicitly since we import the derive macros.

Since commit 70975d06 (remove unused macro_rules and macro_use,
2019-07-30) we no longer use the `serde_derive` crate.

70975d06 remove unused macro_rules and macro_use
862babe2

 impl const fn method
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !155

2ea7680c types: Expose the event target from resource label events
e0312dcf

 types: Add resource label events
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !152

5f36535a

 error: Look for 'error' field in Gitlab error objects
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !153

Some errors from Gitlab put the message in an `error` member
instead of `message`.

This will expose the merge issue id or the issue id of the MR/issue on
which the resource label event was created.

Resource label events record are events that are recorded whenever a
label is added or removed to an issue/merge request.

This Gitlab API was added in 11.1, and so any labels added/removed
before this release will not appear in the data returned by this API.

fdae599c

 types: update for 12.0
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !151

Projects gained a field indicating whether they have an empty repo.
Issues gained a field indicating whether there is an empty task list.

Issues and MRs also gained a field for task completion, but we leave
that unimplemented for now.

* release-11.11:
  cargo: prep for 0.1111.0
  cargo: prep for 0.1110.0
  cargo: prep for 0.1109.1
  cargo: prep for 0.1109.0
  cargo: prep for 0.1108.0
  cargo: prep for 0.1107.0
  cargo: prep for 0.1106.0
  cargo: prep for 0.1105.0
  webhooks: source_project_id is null if the source repo is deleted