<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gitea-Collaborator-Management on Agent Zone</title><link>https://agent-zone.ai/skills/gitea-collaborator-management/</link><description>Recent content in Gitea-Collaborator-Management on Agent Zone</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agent-zone.ai/skills/gitea-collaborator-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Gitea Collaborator Grants and Review Officiality</title><link>https://agent-zone.ai/knowledge/cicd/gitea-collaborator-trap/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/cicd/gitea-collaborator-trap/</guid><description>&lt;p&gt;A pull request has two &lt;code&gt;state: APPROVED&lt;/code&gt; reviews from different reviewers. Branch protection requires &lt;code&gt;required_approvals: 1&lt;/code&gt;. The merge attempt returns &lt;code&gt;HTTP 405 — &amp;quot;Does not have enough approvals&amp;quot;&lt;/code&gt;. The protection config looks correct, the reviews look correct, and the error message looks misleading. The actual root cause is hidden in a field most operators never check: &lt;code&gt;official&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id="what-official-means"&gt;What &lt;code&gt;official&lt;/code&gt; means&lt;a class="anchor" href="#what-official-means"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Every Gitea review carries an &lt;code&gt;official&lt;/code&gt; boolean. Branch protection&amp;rsquo;s &lt;code&gt;required_approvals&lt;/code&gt; counts only reviews where &lt;code&gt;official: true&lt;/code&gt;. A reviewer&amp;rsquo;s APPROVE only flips to &lt;code&gt;official: true&lt;/code&gt; if they were a &lt;strong&gt;write-level repository collaborator&lt;/strong&gt; at the moment the review was filed.&lt;/p&gt;</description></item></channel></rss>