…ue queue (#338) * feat: support GitLab work items for projects that have migrated off the Drupal.org issue queue Projects with `field_project_has_issue_queue: false` now route through `glab` CLI instead of the Drupal.org API. - Add `hasIssueQueue` to `Project` entity - Add `WorkItemRef` to parse `git.drupalcode.org/-/work_items/{id}` URLs - Add `GetGitLabIssueAction` and `ListGitLabIssuesAction` (glab subprocess) - Add `GitLabIssueResult` / `GitLabIssuesResult` with full formatter support - `issue:show` detects GitLab URLs and delegates to glab - `project:issues` delegates to glab when project has no D.o issue queue - Register `gitlab_issue_show` and `gitlab_project_issues` MCP tools Closes #335, closes #337 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * refactor: use GitLab HTTP API instead of glab subprocess for issue reads GetGitLabIssueAction and ListGitLabIssuesAction now use the existing GitLab\Client (Guzzle) instead of shelling out to glab. Public projects on drupalcode.org require no auth; private projects use DRUPALORG_GITLAB_TOKEN when set. This removes the glab dependency for all read operations. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat: accept GitLab work item URLs in issue:get-fork and related commands IssueCommandBase now detects work item URLs (git.drupalcode.org/-/work_items), extracts the numeric NID and stores a WorkItemRef. GetIssueForkAction accepts an optional project machine name to skip the D.o node lookup, which fails for GitLab-native work items that have no field_project on drupal.org. issue:get-fork https://git.drupalcode.org/project/ai_context/-/work_items/3586157 mr:list https://git.drupalcode.org/project/ai_context/-/work_items/3586157 Both now resolve the issue fork and project MRs correctly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: update README with current command list and GitLab work items support Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * refactor: rename WorkItemUrl back to WorkItemRef, add shorthand format WorkItemRef better matches MergeRequestRef's naming convention. Also adds shorthand notation so users can reference work items without full URLs: ai_context#3586157 (project/ prefix assumed) project/ai_context#3586157 (explicit path) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: add WorkItemRef shorthand formats to README Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs(skills): update all skills for GitLab work items support - drupalorg-work-on-issue: accept WorkItemRef inputs (NID, shorthand, URL) - drupalorg-cli: document WorkItemRef formats, GitLab project auto-detection, updated error table with GitLab-specific errors - drupalorg-issue-search: detect GitLab work item projects and skip D.o channels - drupalorg-issue-summary-update: early-exit with clear message for GitLab work items Closes #337 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix: synthesize MergeRequestRef from WorkItemRef in MrCommandBase mr:status, mr:diff, mr:files, and mr:logs all pass $this->mrRef to their actions. When a WorkItemRef is parsed by IssueCommandBase, mrRef was never set, so actions fell through to resolveGitLabProject() which fails for GitLab work item projects (no field_project on the D.o node). Synthesizing a MergeRequestRef from the WorkItemRef's projectPath causes actions to use resolveFromRef() instead, which queries GitLab directly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Uh oh!

Figure out support for projects using GitLab issues #335

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions