The standard way to give deps write-access to your repo is with a personal access token. You can use your personal account to do this, or a "bot" account that your team has.
write_repository
and api
scopes
DEPS_GITLAB_TOKEN
environment variable in your CIWhen working with a GitLab repo, there are a few settings you can use to determine what your MRs look like.
version: 3
dependencies:
- type: python
settings:
gitlab_target_branch: "dev"
gitlab_labels: ["automerge"]
gitlab_assignee_id: 1
gitlab_assignee_ids: [1, 2]
gitlab_target_project_id: 1
gitlab_milestone_id: 1
gitlab_remove_source_branch: true
gitlab_allow_collaboration: true
gitlab_allow_maintainer_to_push: true
gitlab_squash: true
If you don't need a deps.yml
then you can also configure these settings via environment variables.
This is an easy way to put settings directly in your CI config.
Note that they'll need to be in the format of a JSON-encoded string,
with an uppercase name prefixed by DEPS_SETTING_
.
$ DEPS_SETTING_GITLAB_LABELS='["automerge"]' deps ci