aboutsummaryrefslogtreecommitdiffstats
path: root/modules/git/tests/repos/repo1_bare
diff options
context:
space:
mode:
authorInfinoid <mark@glines.org>2023-08-24 01:36:04 -0400
committerGitHub <noreply@github.com>2023-08-24 05:36:04 +0000
commit86ee5b4b1b6acdba89912a3c89c39f9948e67f07 (patch)
treed8426cb40bbb133f7505b511ae9ac07bae5deb5e /modules/git/tests/repos/repo1_bare
parentd2e4039def61d9cc9952be462216001125327270 (diff)
downloadgitea-86ee5b4b1b6acdba89912a3c89c39f9948e67f07.tar.gz
gitea-86ee5b4b1b6acdba89912a3c89c39f9948e67f07.zip
PATCH branch-protection updates check list even when checks are disabled (#26351)
Fixes: #26333. Previously, this endpoint only updates the `StatusCheckContexts` field when `EnableStatusCheck==true`, which makes it impossible to clear the array otherwise. This patch uses slice `nil`-ness to decide whether to update the list of checks. The field is ignored when either the client explicitly passes in a null, or just omits the field from the json ([which causes `json.Unmarshal` to leave the struct field unchanged](https://go.dev/play/p/Z2XHOILuB1Q)). I think this is a better measure of intent than whether the `EnableStatusCheck` flag was set, because it matches the semantics of other field types. Also adds a test case. I noticed that [`testAPIEditBranchProtection` only checks the branch name](https://github.com/go-gitea/gitea/blob/c1c83dbaec840871c1247f4bc3f875309b0de6bb/tests/integration/api_branch_test.go#L68) and no other fields, so I added some extra `GET` calls and specific checks to make sure the fields are changing properly. I added those checks the existing integration test; is that the right place for it?
Diffstat (limited to 'modules/git/tests/repos/repo1_bare')
0 files changed, 0 insertions, 0 deletions