Skip to content

Add Gitea Notifications#2787

Closed
bircni wants to merge 2 commits intogitify-app:mainfrom
bircni:cursor/gitea-forge-support
Closed

Add Gitea Notifications#2787
bircni wants to merge 2 commits intogitify-app:mainfrom
bircni:cursor/gitea-forge-support

Conversation

@bircni
Copy link
Copy Markdown

@bircni bircni commented Apr 18, 2026

Add the option to also add gitea notifications
grafik

@bircni bircni changed the title Fix Gitea mark-as-done and unsubscribe behavior Add Gitea Notifications Apr 18, 2026
Copy link
Copy Markdown
Member

@setchy setchy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At this time, supporting other git platforms is not on our roadmap (see CONTRIBUTING.md)

@afonsojramos
Copy link
Copy Markdown
Member

@setchy to be honest, looking at the implementation (just reviewing the code, haven't really test) it doesn't really seem to create any Gitea-specific concepts. In the past, bitbucket has definitely steered far from what we had for GH, but gitea doesn't seem to differ as much

@setchy
Copy link
Copy Markdown
Member

setchy commented Apr 24, 2026

@setchy to be honest, looking at the implementation (just reviewing the code, haven't really test) it doesn't really seem to create any Gitea-specific concepts.

Same, I too have done a quick code review but haven't tested it. Took me a minute to work out what forge was being used for 😄

In the past, bitbucket has definitely steered far from what we had for GH, but gitea doesn't seem to differ as much

Actually, Bitbucket-only notifications could be a clean fit too... it was just that there are also many other Atlassian products [non-git] which had valuable notifications.


I think my primary hesitation is the overhead on the maintainers to support more git platforms.

In concept, I like it. In practice, there will be a "cost"...

It would also make us question whether the use of things like Octicons, Octokit, Primer Design System still makes sense...

@afonsojramos
Copy link
Copy Markdown
Member

It would also make us question whether the use of things like Octicons, Octokit, Primer Design System still makes sense...

Fair, but we are lacking the design skills to do something from scratch 😅 It should be fine

I think my primary hesitation is the overhead on the maintainers to support more git platforms.

It should be fine if we have someone responsible for that section. In this case, @bircni 👀 Other apps that consider themselves as mutli-platform also have dedicated maintainers for each OS, to validate that everything is working.

Actually, Bitbucket-only notifications could be a clean fit too... it was just that there are also many other Atlassian products [non-git] which had valuable notifications.

Well then 👀

@bircni bircni force-pushed the cursor/gitea-forge-support branch from 8834792 to e9e478e Compare May 1, 2026 20:29
@bircni
Copy link
Copy Markdown
Author

bircni commented May 1, 2026

rebased onto main - idk how we want to proceed here
I really like the app and gitea notifications are a gamechanger for me here

@afonsojramos
Copy link
Copy Markdown
Member

@bircni let's just take a step back and evaluate multi-platform, maybe this can be architectured in a different way.

@setchy
Copy link
Copy Markdown
Member

setchy commented May 6, 2026

#2841

afonsojramos added a commit that referenced this pull request May 6, 2026
Adds the first non-GitHub forge adapter under the new ForgeAdapter
contract: client (fetch-based, no Octokit), types, transform, and
adapter registration. Wires Gitea PAT login into the Login and Accounts
routes, exposes the Gitea platform icon, and gates unsupported actions
(mark-as-done, unsubscribe, GraphQL enrichment) via capability flags.

Adapted from work originally proposed in #2787.

Co-authored-by: bircni <75789103+bircni@users.noreply.github.com>
@setchy
Copy link
Copy Markdown
Member

setchy commented May 6, 2026

thanks @bircni

now superseded by forge adapters in #2842

@setchy setchy closed this May 6, 2026
@bircni bircni deleted the cursor/gitea-forge-support branch May 6, 2026 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants