You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Display new commits, releases and issues in each seperate bridge like we have for github. GitHub has already atom feeds, gogs/gitea does not have it and we need it.
Host URI for the bridge (i.e. https://github.com):
universal, user should can add the instance url
Which information would you like to see?
Issues
Commits
Releases
How should the information be displayed/formatted?
Like on GitHub bridge, just simple
Which of the following parameters do you expect?
Title
URI (link to the original article)
Author
Timestamp
Content (the content of the article)
Enclosures (pictures, videos, etc...)
Categories (categories, tags, etc...)
Options
Limit number of returned items
Default limit: 5
Load full articles
Cache articles (articles are stored in a local cache on first request): yes
Cache timeout (max = 24 hours): 24 hours
Balance requests (RSS-Bridge uses cached versions to reduce bandwith usage)
I don't use Gitea, but it sees to work with their test servers (except releases): https://try.gitea.io
As long as they share the same code base everything should work fine. I'm sure they'll diverge at some point in which case a separate bridge for Gitea is needed. Let me add another bridge for Gitea for maintainability reasons.
Bridge request
Bridge request for Gogs and/or Gitea
General information
Display new commits, releases and issues in each seperate bridge like we have for github. GitHub has already atom feeds, gogs/gitea does not have it and we need it.
Host URI for the bridge (i.e.
https://github.com
):universal, user should can add the instance url
Which information would you like to see?
Issues
Commits
Releases
How should the information be displayed/formatted?
Like on GitHub bridge, just simple
Which of the following parameters do you expect?
Options
The text was updated successfully, but these errors were encountered: