feat(forge): add GitLab support - #3225
Merged
afonsojramos merged 12 commits intoAug 26, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Copy link
Copy Markdown
|
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
Great work @afonsojramos - our forges continue to go from strength to strength. I don't have a GitLab handy to test on, but lgtm |
Sorry, something went wrong.
setchy
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds GitLab (Cloud and Self-Managed) as a forge behind the existing ForgeAdapter interface, with no forge-specific branching outside src/renderer/utils/forges/gitlab/. GitLab has no /notifications endpoint, so the adapter is built on the To-Do API — and because a to-do embeds its full target object, enrichNotifications is omitted entirely and one list call carries everything the detailed-notifications setting needs. GitLab also has no read/unread axis (only pending/done), so capabilities.markAsDone reports false and mark-as-read maps onto POST /todos/:id/mark_as_done, keeping the row to a single button.
Worth flagging for review: clearing a to-do needs the broad api scope on legacy tokens (or the Todo resource on GitLab 18+ fine-grained tokens), and To-Do items are narrower than GitHub notifications — both are stated on the login screen. Every API behaviour was verified against live gitlab.com rather than taken from the docs, and the feature was exercised end-to-end in the app: login, render, mark-as-read round-trip, and logout.
Closes #237