Wherever a branch name is shown, its open Gitea pull request stands
beside it, linked to the pull request. The watcher reads the open pull
requests once per poll cycle into PullRequestIndex; pages and API only
read from there. Needs the Gitea connection and token; forks, private
repositories for visitors, and gone branches show none.
Wherever a branch name is shown, its open Gitea pull request stands
beside it, linked to the pull request. The watcher reads the open pull
requests once per poll cycle into PullRequestIndex; pages and API only
read from there. Needs the Gitea connection and token; forks, private
repositories for visitors, and gone branches show none.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Wherever a branch name is shown, its open Gitea pull request stands
beside it, linked to the pull request. The watcher reads the open pull
requests once per poll cycle into PullRequestIndex; pages and API only
read from there. Needs the Gitea connection and token; forks, private
repositories for visitors, and gone branches show none.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Wherever a branch name is shown, its open Gitea pull request stands
beside it, linked to the pull request. The watcher reads the open pull
requests once per poll cycle into PullRequestIndex; pages and API only
read from there. Needs the Gitea connection and token; forks, private
repositories for visitors, and gone branches show none.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com