Skip to content

fix(edge-worker): thread apiBaseUrl into GitLabCommentService for Self-Managed GitLab#1191

Open
tenfourty wants to merge 2 commits into
cyrusagents:mainfrom
tenfourty:feat/self-managed-apibaseurl
Open

fix(edge-worker): thread apiBaseUrl into GitLabCommentService for Self-Managed GitLab#1191
tenfourty wants to merge 2 commits into
cyrusagents:mainfrom
tenfourty:feat/self-managed-apibaseurl

Conversation

@tenfourty
Copy link
Copy Markdown

Summary

GitLabCommentService accepts an optional apiBaseUrl in its constructor, but EdgeWorker was instantiating it with no args. On a Self-Managed GitLab every MR-reply request was hitting gitlab.com and 404'ing — the only obvious signal was a steady stream of 404s in the logs.

This derives apiBaseUrl from the URL origin of the first configured repo with a gitlabUrl. Single GitLab host per Cyrus instance — multi-host per-repo dispatch is out of scope here.

Test plan

  • pnpm test:packages:run — all package tests pass
  • pnpm typecheck — clean
  • pnpm lint — clean on the changed file
  • Verified end-to-end on a Self-Managed GitLab instance: MR replies now post against the configured host instead of 404'ing on gitlab.com

tenfourty and others added 2 commits May 12, 2026 15:33
…f-Managed GitLab

GitLabCommentService accepts an optional apiBaseUrl in its constructor but
EdgeWorker was instantiating it with no args, leaving it pinned to the
gitlab.com default. On Self-Managed instances every MR-reply request 404s.

Derive apiBaseUrl from the URL origin of the first configured repo with
a gitlabUrl. Single GitLab host per Cyrus instance — multi-host per-repo
dispatch is out of scope.
@tenfourty tenfourty force-pushed the feat/self-managed-apibaseurl branch from ce20807 to 9d1f493 Compare May 12, 2026 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant