[Bug] merge_pull_request returns 422 due to wrong parameter name (merge_strategy vs do) #5

New Issue

xcaliber · 2026-01-15T13:49:12Z

xcaliber commented

2026-01-15 13:49:12 +00:00

Description:
The merge_pull_request tool in gitea/dev.py returns HTTP 422 error when attempting to merge pull requests.

Expected Behavior:
PR should merge successfully when using the tool.

Actual Behavior:

HTTP Error 422: [Do]: Required

Root Cause:
Gitea API expects a do parameter (e.g., {"do": "merge"}), but the tool is sending merge_strategy as the parameter name.

Proposed Fix:
Update the merge_pull_request function to send {"do": "merge"} instead of {"merge_strategy": "merge"} in the request body.

Affected File:
open-webui-automation/tools/gitea/dev.py

Severity:
Medium - Blocks PR merging operations.

**Description:** The `merge_pull_request` tool in `gitea/dev.py` returns HTTP 422 error when attempting to merge pull requests. **Expected Behavior:** PR should merge successfully when using the tool. **Actual Behavior:** ``` HTTP Error 422: [Do]: Required ``` **Root Cause:** Gitea API expects a `do` parameter (e.g., `{"do": "merge"}`), but the tool is sending `merge_strategy` as the parameter name. **Proposed Fix:** Update the `merge_pull_request` function to send `{"do": "merge"}` instead of `{"merge_strategy": "merge"}` in the request body. **Affected File:** `open-webui-automation/tools/gitea/dev.py` **Severity:** Medium - Blocks PR merging operations.

xcaliber referenced this issue from a commit

2026-01-15 13:53:05 +00:00

fix(merge_pull_request): change merge_strategy to do parameter for Gitea API

xcaliber referenced a pull request that will close this issue

2026-01-15 17:12:31 +00:00

fix: merge_pull_request uses wrong parameter name (do vs merge_strategy) #6

xcaliber referenced this issue

2026-01-17 13:36:11 +00:00

Deprecate gitea_dev Role #18

xcaliber referenced this issue

2026-01-17 13:36:16 +00:00

Manual Workflow Validation #19