mirror of
https://github.com/go-gitea/gitea.git
synced 2026-10-23 19:43:59 +09:00
Backport #39885 by @basavaraj-sm05 Several `/repos/{owner}/{repo}/issues/{index}/...` API endpoints load the issue by index without checking `CanReadIssuesOrPulls(issue.IsPull)`, unlike `GetIssue`, `ListIssueComments` and `GetIssueReactions`. The route group's `mustEnableIssuesOrPulls` passes when the caller can read either unit, so someone who can read issues but not pull requests (a team with only the Issues unit, or per-unit anonymous access on a public repo) can read a pull request's whole conversation through `/timeline`, plus its labels, subscribers, attachments and tracked times, and can subscribe to it. The reverse holds for issues. These handlers now return 404 in that case, like their siblings. Co-authored-by: Basavaraj S m <basavaraj@digiscrypt.com> Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>