Checkout in release.yml now uses \`secrets.RELEASE_TOKEN\` (Gitea bot PAT) instead of \`GITHUB_TOKEN\`, which branch protection on main rejects.
Closes #41
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The built-in GITHUB_TOKEN is rejected by branch protection on main.
Use the Gitea bot's RELEASE_TOKEN, which may bypass it.
Closes#41
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Here are some key observations to aid the review process:
⏱️Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪No relevant tests
🔒No security concerns identified
⚡No major issues detected
## PR Reviewer Guide 🔍
<!-- pr-agent:review:full -->
Here are some key observations to aid the review process:
<table>
<tr><td>⏱️ <strong>Estimated effort to review</strong>: 1 🔵⚪⚪⚪⚪</td></tr>
<tr><td>🧪 <strong>No relevant tests</strong></td></tr>
<tr><td>🔒 <strong>No security concerns identified</strong></td></tr>
<tr><td>⚡ <strong>No major issues detected</strong></td></tr>
</table>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Checkout in release.yml now uses `secrets.RELEASE_TOKEN` (Gitea bot PAT) instead of `GITHUB_TOKEN`, which branch protection on main rejects.
Closes #41
🤖 Generated with Claude Code
Failed to update PR description
PR Reviewer Guide 🔍
Here are some key observations to aid the review process:
PR Code Suggestions ✨
No code suggestions found for the PR.