| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
chore: enable mypy check `warn_return_any`
|
| |
| |
| |
| | |
Update code so that the `warn_return_any` check passes.
|
|\ \
| | |
| | | |
chore: make code PEP597 compliant
|
| |/
| |
| |
| |
| |
| | |
Use `encoding="utf-8"` in `open()` and open-like functions.
https://peps.python.org/pep-0597/
|
|\ \
| |/
|/| |
test(functional): bump GitLab docker image to 15.2.0-ee.0
|
| |
| |
| |
| | |
In GitLab >= 15.0 `title` is required when creating a topic.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. If a value is of type ArrayAttribute then append '[]' to the name
of the value for query parameters (`params`).
This is step 3 in a series of steps of our goal to add full
support for the GitLab API data types[1]:
* array
* hash
* array of hashes
Step one was: commit 5127b1594c00c7364e9af15e42d2e2f2d909449b
Step two was: commit a57334f1930752c70ea15847a39324fa94042460
Fixes: #1698
[1] https://docs.gitlab.com/ee/api/#encoding-api-parameters-of-array-and-hash-types
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Use `monkeypatch` to ensure that no config files are reported for the
test.
Closes: #2172
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
feat: add `asdict()` and `to_json()` methods to Gitlab Objects
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add an `asdict()` method that returns a dictionary representation copy
of the Gitlab Object. This is a copy and changes made to it will have
no impact on the Gitlab Object.
The `asdict()` method name was chosen as both the `dataclasses` and
`attrs` libraries have an `asdict()` function which has the similar
purpose of creating a dictionary represenation of an object.
Also add a `to_json()` method that returns a JSON string
representation of the object.
Closes: #1116
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the `attributes` method would show the original values in a
Gitlab Object even if they had been updated. Correct this so that the
updated value will be returned.
Also use copy.deepcopy() to ensure that modifying the dictionary returned can
not also modify the object.
|
|/
|
|
|
|
|
|
| |
This can be used to tell if a `RESTObject` was created using
`lazy=True`.
Add a message to the `AttributeError` if attribute access fails for an
instance created with `lazy=True`.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Add support for validating a project's CI configuration [1]
[1] https://docs.gitlab.com/ee/api/lint.html
|
|
|
|
|
|
| |
Add the GroupPushRules and GroupPushRulesManager classes.
Closes: #1259
|
|\
| |
| | |
test(projects): add unit tests for projects
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In GitLab 14.10 they added support to get a single merge request
approval rule [1]
Add support for it to ProjectMergeRequestApprovalRuleManager
[1] https://docs.gitlab.com/ee/api/merge_request_approvals.html#get-a-single-merge-request-level-rule
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Commit b6447211754e126f64e12fc735ad74fe557b7fb4 inadvertently
introduced a possible breaking change as it added a new argument
`iterator` and added it in between existing (potentially positional) arguments.
This moves the `iterator` argument to the end of the argument list and
requires it to be a keyword-only argument.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* feat(downloads): allow streaming downloads access to response iterator
Allow access to the underlying response iterator when downloading in
streaming mode by specifying `iterator=True`.
Update type annotations to support this change.
* docs(api-docs): add iterator example to artifact download
Document the usage of the `iterator=True` option when downloading
artifacts
* test(packages): add tests for streaming downloads
|
|\ \
| | |
| | | |
feat(users): add approve and reject methods to User
|
| | |
| | |
| | |
| | |
| | |
| | | |
As requested in #1604.
Co-authored-by: John Villalovos <john@sodarock.com>
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| | |
- https://docs.gitlab.com/ee/api/protected_environments.html
- https://github.com/python-gitlab/python-gitlab/issues/1130
no write operation are implemented yet as I have no use case right now
and am not sure how it should be done
|
| | |
|
|\ \
| |/
|/| |
fix(cli): project-merge-request-approval-rule
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using the CLI the command:
gitlab project-merge-request-approval-rule list --mr-iid 1 --project-id foo/bar
Would raise an exception. This was due to the fact that `_id_attr` and
`_repr_attr` were set for keys which are not returned in the response.
Add a unit test which shows the `repr` function now works. Before it
did not.
This is an EE feature so we can't functional test it.
Closes: #2065
|