lucidiot/rsrsss
lucidiot
/
rsrsss
2
1
Fork 0
Code Issues Releases Activity

Post about Gitea 1.17

This commit is contained in:
~lucidiot 2022-08-08 02:20:38 +02:00
parent 02b2a5cf5a
commit fe2c4b5ba9
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
feed.xml
View File

@ -836,5 +836,23 @@
<p>And if, like me, you are using an <abbr title="eXtensible Stylesheet Language Transformation">XSLT</abbr> as your <a href="https://www.w3.org/TR/xml-stylesheet/" target="_blank"><code>&lt;?xml-stylesheet?&gt;</code></a>, you could add a link to report errors with your feed if someone is displaying it in a browser. If you open RSRSSS in your web browser and your browser does not have native support for RSS feeds, then you can find this link at the very bottom of the page.</p>
]]></description>
</item>
<item>
<title>Gitea has most feeds, except the most important one</title>
<pubDate>Mon, 08 Aug 2022 01:28:03 +0200</pubDate>
<guid isPermaLink="false">gitea-most-feeds</guid>
<category domain="https://envs.net/~lucidiot/rsrsss/">Tip</category>
<description><![CDATA[
<p>While Gitea's 1.16.0 release <a href="https://github.com/go-gitea/gitea/pull/16002" target="_blank">added support for user feeds</a>, it was laching the feeds for repositories, organizations, releases and commits. The 1.17.0 release <a href="https://github.com/go-gitea/gitea/pull/19055" target="_blank">adds support for feeds on repositories</a> and <a href="https://github.com/go-gitea/gitea/pull/17714" target="_blank">adds support for feeds on organizations</a>, but the feed for releases, the most well-known and most commonly used feed on GitHub, is still missing.</p>
<p>As mentioned earlier when I talked about the 1.16.0 release, the feeds are accessible either by setting the <code>Accept</code> header to <code>application/rss+xml</code> or <code>application/atom+xml</code> when requesting a user, an organization or a repository's URL, or by appending .rss or .atom to the username, repository name or organization name. Some examples:</p>
<ul>
<li>The <a href="https://tildegit.org/lucidiot.rss" target="_blank">RSS feed</a> and the <a href="https://tildegit.org/lucidiot.atom" target="_blank">Atom feed</a> for my account on <a href="https://tildegit.org" target="_blank">Tildegit</a>, the Gitea instance of the <a href="https://tildeverse.org" target="_blank">Tildeverse</a>;</li>
<li>The <a href="https://tildegit.org/lucidiot/rsrsss.rss" target="_blank">RSS feed</a> and the <a href="https://tildegit.org/lucidiot/rsrsss.atom" target="_blank">Atom feed</a> for the repository hosting RSRSSS;</li>
<li>The <a href="https://tildegit.org/casa.rss" target="_blank">RSS feed</a> and the <a href="https://tildegit.org/casa.atom" target="_blank">Atom feed</a> for the <a href="https://casa.tildepages.org" target="_blank">Commonhealth of Casakhstan</a>'s Gitea organization on Tildegit.</li>
</ul>
<p>I hope that we will see <a href="https://github.com/go-gitea/gitea/issues/19091" target="_blank">the feeds for releases</a> in the next release, so that Gitea adds the one missing feature to make package maintainers happy.</p>
<p>By the way, <a href="https://tildegit.org/lucidiot/rsrsss.rss" target="_blank">the RSS feed for the RSRSSS repo</a> could be called the Really Simple RSRSSS Repository Syndication feed, or <abbr title="Really Simple Really Simple Really Simple Syndication Syndication Repository Syndication">RSRSRSSSRS</abbr>.</p>
]]></description>
</item>
</channel>
</rss>