silverwind 761b9d439b Fix API not persisting pull request unit config when has_pull_requests is not set (#36718) ... The `PATCH /api/v1/repos/{owner}/{repo}` endpoint silently ignores pull request config fields (like `default_delete_branch_after_merge`, `allow_squash_merge`, etc.) unless `has_pull_requests: true` is also included in the request body. This is because the entire PR unit config block was gated behind `if opts.HasPullRequests != nil`. This PR restructures the logic so that PR config options are applied whenever the pull request unit already exists on the repo, without requiring `has_pull_requests` to be explicitly set. A new unit is only created when `has_pull_requests: true` is explicitly sent. Fixes https://github.com/go-gitea/gitea/issues/36466 Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Giteabot <teabot@gitea.io>		2026-03-02 22:08:53 +00:00
..
option_test.go	Fix updating user visibility (#35036)	2025-07-10 16:17:28 -07:00
option.go	Fix API not persisting pull request unit config when has_pull_requests is not set (#36718)	2026-03-02 22:08:53 +00:00
serialization_test.go	use experimental go json v2 library (#35392)	2025-09-28 08:03:36 +00:00
serialization.go	Enable nilnil linter for new code (#36591)	2026-02-16 09:57:18 +00:00