The Darwin Project Blackboard Darwin Gitlab Ops

GitLab Operations

Project Resolution (CRITICAL)

When working on an Event from the Headhunter, the event document contains the authoritative project path and MR URL in the GitLab Context section. Use THAT project path and MR URL for all API calls.

Use the Service Lookup only for check Aligner events or when a user asks.

Extract from the event document:

• MR URL -- use this for the target MR
• Project -- use this as the project path for API calls

Pre-Configured Environment

GitLab CLI tools and MCP tools are pre-configured via $GITLAB_HOST. TLS behavior is controlled by the deployment environment. You do not need to handle authentication setup.

Available environment variables:

• GITLAB_TOKEN -- Personal Access Token for API calls
• GITLAB_HOST -- The GitLab hostname

Git operations to $GITLAB_HOST use the pre-configured TLS settings.

Tool Preference

GitLab MCP tools are available in your tool list. Prefer them for structured API interactions -- they handle authentication and pagination automatically. CLI and direct API access are available as fallback.

URL-Encoding for Nested Project Paths

GitLab API requires URL-encoded project paths for nested groups. For example, org/group/subgroup/project must be encoded as org%2Fgroup%2Fsubgroup%2Fproject. Ensure project paths are properly encoded when constructing API requests.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.