-
Currently running hookshot v5.3.0.
I configured the GitLab integration and bridged a room using the message.
```
!hookshot gitlab project https://git.example.com/group/project
```
It succes…
-
- Only delivering the gitlab changes after some days or similar
- Not delivering pending messages on chronological order (Random time order)
-
As a UDS package engineer
I need the GitLab Runner to use renovate bot
So that upstream dependency updates are automatically included in the GitLab-Runner package
-
After change `Merge requests` settings to only display merge events bot still send messages about opening MR.
![image](https://user-images.githubusercontent.com/1986478/30852711-5e495896-a2b5-11e7-…
-
-
### Problem Statement
Currently, when issues are created in GitLab via Sentry, they are always created under the administrator's username who set up the integration. This leads to confusion in issue …
-
The Gitlab LDAP sync script tries to currently remove "bot users" that are created when adding an `access_token` from non-ldap groups. Maybe even from groups that are also present in LDAP.
`https:/…
-
### Summary
CI/CD variables can have a description, which I'd like to set it via Ansible.
![grafik](https://github.com/ansible-collections/community.general/assets/22525368/5620e4e7-6751-4b8d-91ab…
-
## Description
This is a relatively new feature of Gitlab where you can create a project access token that further creates a bot user that allows you to interact with the git repo and gitlab API. …
-
**Background**:
- current command bot is fully dependent on GitLab, because it was designed to manage tasks queue via GitLab CI pipelines.
- if any parachain team would want to re-use this bot for the…