Skip to content

docs: exploring multi git platform support #2841

@setchy

Description

@setchy

Note

The below table has been generated with the help of Gemini.
Further refinement, exploration and prioritization are required.

Git Platform Notification Support

Platform Notifications API Primary Method Implementation Notes
GitHub ✅ Yes REST (/notifications) Server-side "Read" state and thread-based grouping.
Bitbucket Cloud ✅ Yes GraphQL Uses the workActivity and notifications query via Atlassian Gateway.
GitLab ✅ Yes REST (/todos) The /todos API is the best "Inbox" equivalent; /events for raw activity.
Gitea ✅ Yes REST (/notifications) Dedicated endpoint for user-specific notification feeds.
Forgejo ✅ Yes REST (/notifications) Currently maintains Gitea compatibility but adding unique OIDC/Federation hooks.
Azure DevOps ⚠️ Partial REST No unified feed; requires polling specific projects and pullRequests.
Gerrit ❌ No REST Change-set focused; requires custom polling of the /changes/ API.
AWS CodeCommit ❌ No SDK/EventBridge No user-facing inbox API; purely event-driven infrastructure.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions