Hello,
An RSS feed is GOLD to recieve alerts when a repo is pushed to or some action. Is there any chance this could be added to Codeberg?
Thanks.
---
upstream: https://github.com/go-gitea/gitea/issues/569
At this moment, to get alerts for repositories there's also the possibility to "watch" a repository by clicking the button with the "eye" icon when in a repository (see enclosed screenshot). When you watch a repo, you'll get an email for example for new issues, PRs and comments.
That's a very nice idea :) And there's already a feature request for Gitea: https://github.com/go-gitea/gitea/issues/569
At this moment, to get alerts for repositories there's also the possibility to "watch" a repository by clicking the button with the "eye" icon when in a repository (see enclosed screenshot). When you watch a repo, you'll get an email for example for new issues, PRs and comments.
I endorse this request. Being able to follow the workflow using tools like Newsboat or RssTail would be magnificent.
Looking forward to this implementation.
I endorse this request. Being able to follow the workflow using tools like **Newsboat** or **RssTail** would be magnificent.
Looking forward to this implementation.
would be nice if I can get suggestions ... - anybody here who can compile gitea and want to try it?
on https://github.com/go-gitea/gitea/pull/16002 is kind a "ready"
would be nice if I can get suggestions ... - anybody here who can compile gitea and want to try it?
The proposed implementation here seems ideal in terms of enabling the use of isolated feeds that display events from their associated Gitea data views. At least in part, have you gone for this proposal @6543?
The proposed implementation [here](https://github.com/go-gitea/gitea/issues/569#issuecomment-729615790) seems ideal in terms of enabling the use of isolated feeds that display events from their associated Gitea data views. At least in part, have you gone for this proposal @6543?
@JackDandy only rss/atom feed for the feed you have on UI now
after that I'll have to refactor functions to be more flexible and than I can do per org or repo
for commits this is another issue i would say
@JackDandy only rss/atom feed for the feed you have on UI now
after that I'll have to refactor functions to be more flexible and than I can do per org or repo
for commits this is another issue i would say
only rss/atom feed for the feed you have on UI now
I'm sorry, I was not very clear in my question, and therefore, the answer wasn't either, let me try again...
What event(s) is published to the feed created by your PR ?
> only rss/atom feed for the feed you have on UI now
I'm sorry, I was not very clear in my question, and therefore, the answer wasn't either, let me try again...
What event(s) is published to the feed created by your PR ?
If no push commit events are posted to the rss feed, then my OP stands as a feature request.
I think most of us are looking forward to when your PR handles that ;)
I now understand better (I failed to last night, sorry).
Thanks for your efforts.
> for commits this is another issue
If no ***push commit*** events are posted to the rss feed, then my OP stands as a feature request.
I think most of us are looking forward to when your PR handles that ;)
I now understand better (I failed to last night, sorry).
Thanks for your efforts.
I think the question was if more RSS feeds are available than the initial implementation. I honestly don't think so, AFAIK the idea was that this is a reference implementation where other contributors can build upon, but no one seemed interested in doing this yet. But maybe I missed some Gitea PRs in the meantime.
I think the question was if more RSS feeds are available than the initial implementation. I honestly don't think so, AFAIK the idea was that this is a reference implementation where other contributors can build upon, but no one seemed interested in doing this yet. But maybe I missed some Gitea PRs in the meantime.
No, @rwa got my question right. I erroneously assumed this feature was included in the latest release since it was merged ~2 week before the release. Thanks!
No, @rwa got my question right. I erroneously assumed this feature was included in the latest release since it was merged ~2 week before the release. Thanks!
Would be really helpful to have that similar to how github allows adding .atom to the url of a releases page to get an RSS/atom feed.
What about release RSS feeds?
Would be really helpful to have that similar to how github allows adding `.atom` to the url of a releases page to get an RSS/atom feed.
It's tracked upstream ... next version (v1.17.0) will have basic suport (repo/orgs/user)
the basic framework now is in place ... so it's easy to extend it
https://github.com/go-gitea/gitea/issues/19071
It's tracked upstream ... next version (v1.17.0) will have basic suport (repo/orgs/user)
the basic framework now is in place ... so it's easy to extend it
Ok, that's good. There was a discussion in the Codeberg Hackathon about whether to make it RSS orange, but the consensus was that would make it stand out too much, so grey it is :)
Ok, that's good. There was a discussion in the Codeberg Hackathon about whether to make it RSS orange, but the consensus was that would make it stand out _too_ much, so grey it is :)
It's important that this feed should be available on private repos too!
Use case: a couple of us dev on a repo, be nice to get the notification when the other has pushed/committed etc. in our rss alerter.
It's important that this feed should be available on private repos too!
Use case: a couple of us dev on a repo, be nice to get the notification when the other has pushed/committed etc. in our rss alerter.
dont worry the access is just checked as with normal web ... so if there is an active session you can see private feeds too ...
... just wait until codeberg finished testing for v1.17.0
dont worry the access is just checked as with normal web ... so if there is an active session you can see private feeds too ...
... just wait until codeberg finished testing for v1.17.0
Hello,
An RSS feed is GOLD to recieve alerts when a repo is pushed to or some action. Is there any chance this could be added to Codeberg?
Thanks.
upstream: https://github.com/go-gitea/gitea/issues/569
That's a very nice idea :) And there's already a feature request for Gitea: https://github.com/go-gitea/gitea/issues/569
At this moment, to get alerts for repositories there's also the possibility to "watch" a repository by clicking the button with the "eye" icon when in a repository (see enclosed screenshot). When you watch a repo, you'll get an email for example for new issues, PRs and comments.
Sounds like a cool feature (not cluttering the mailbox). Contributions welcome!
+1 would be a great addition to my emacs UI too ^-^
Any news on this?
sadly: no
+1 for this
I endorse this request. Being able to follow the workflow using tools like Newsboat or RssTail would be magnificent.
Looking forward to this implementation.
on https://github.com/go-gitea/gitea/pull/16002 is kind a "ready"
would be nice if I can get suggestions ... - anybody here who can compile gitea and want to try it?
The proposed implementation here seems ideal in terms of enabling the use of isolated feeds that display events from their associated Gitea data views. At least in part, have you gone for this proposal @6543?
well I'd like to do enhancements but for now the initial system has to went in fist
@6543 okay, so what is your initial system from the users perspective?
@JackDandy only rss/atom feed for the feed you have on UI now
after that I'll have to refactor functions to be more flexible and than I can do per org or repo
for commits this is another issue i would say
I'm sorry, I was not very clear in my question, and therefore, the answer wasn't either, let me try again...
What event(s) is published to the feed created by your PR ?
same as you can see on the users ui feed right now
If no push commit events are posted to the rss feed, then my OP stands as a feature request.
I think most of us are looking forward to when your PR handles that ;)
I now understand better (I failed to last night, sorry).
Thanks for your efforts.
Any updates on this since #16002 was merged?
This will be available as soon as the release 1.16 of gitea is finished and the new version has been deployed to codeberg.
I think the question was if more RSS feeds are available than the initial implementation. I honestly don't think so, AFAIK the idea was that this is a reference implementation where other contributors can build upon, but no one seemed interested in doing this yet. But maybe I missed some Gitea PRs in the meantime.
No, @rwa got my question right. I erroneously assumed this feature was included in the latest release since it was merged ~2 week before the release. Thanks!
only for users ... I'm working on repos/orgs:
https://github.com/go-gitea/gitea/pull/17714
witch will finaly close it for good
What about release RSS feeds?
Would be really helpful to have that similar to how github allows adding
.atom
to the url of a releases page to get an RSS/atom feed.https://github.com/go-gitea/gitea/issues/19071
It's tracked upstream ... next version (v1.17.0) will have basic suport (repo/orgs/user)
the basic framework now is in place ... so it's easy to extend it
Can you find the RSS Button on this UI mockup?
@ktprograms Yep
Ok, that's good. There was a discussion in the Codeberg Hackathon about whether to make it RSS orange, but the consensus was that would make it stand out too much, so grey it is :)
It's important that this feed should be available on private repos too!
Use case: a couple of us dev on a repo, be nice to get the notification when the other has pushed/committed etc. in our rss alerter.
dont worry the access is just checked as with normal web ... so if there is an active session you can see private feeds too ...
... just wait until codeberg finished testing for v1.17.0