## Research Question What does the [`gitlab_api`](https://www.drupal.org/project/gitlab_api) contrib module already give us for ingesting GitLab webhooks and calling the GitLab API, and which gaps need to be filed as follow-up issues against that project before we can build the AI Initiative's automation on top of it? ## Background The umbrella issue #3586474 captures the full goal. Whichever platform we choose for orchestration (Rules, ECA, or custom code), it almost certainly should sit on top of `gitlab_api` rather than re-implementing webhook plumbing and an authenticated GitLab REST/GraphQL client. Before we commit, we need an audit of what `gitlab_api` covers today and what we'd be missing. ## Scope **In scope:** - Read the `gitlab_api` module README, code, and existing issue queue. - Install it locally and test: webhook receipt, signature validation, event dispatching, REST/GraphQL helpers. - Identify required behaviors that are missing (e.g. work item / status mutations, MR pipeline event handling, label-management helpers, quick-action–style comment parsing). - File follow-up issues against `gitlab_api` for each gap, with motivation referencing this exploration. **Out of scope:** - Implementing the gaps in `gitlab_api` ourselves (that becomes follow-up work after the issues are filed and prioritized with that project's maintainers). ## Approach - Stand up a fresh Drupal site and enable `gitlab_api`. - Configure a real GitLab project webhook pointing at it; verify each event type relevant to the 7 automations. - For each missing capability, draft a clear, well-scoped issue against `https://www.drupal.org/project/gitlab_api` (or its GitLab repo if that is where its issue queue lives — confirm during the exploration). - Cross-link every filed issue back into this one and into #3586474. ## Deliverables - [x] Audit document: "what `gitlab_api` covers today vs. what we need". - [x] One follow-up issue per identified gap, filed in the `gitlab_api` issue queue. - [x] Updated umbrella issue (#3586474) with the follow-up issue links so the rollout work knows which `gitlab_api` features it depends on. ## Findings <!-- To be filled during and after the investigation. --> ## Related issues ## AI Usage - [x] AI Assisted Issue — This issue was generated with AI assistance, but was reviewed and refined by the creator.