[Schema Inaccuracy] Missing `allow_update_branch` property on `POST /user/repos`

Open Beginner friendly

#5,857 opened on Jan 17, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 68/100

Issue type: Documentation
Clarity: Clearly specified
Activity status: Stale
Tech stack: openapi
Domain: api

Research direction

Start by locating the OpenAPI schema for POST /user/repos and compare it with PATCH /repos/{owner}/{repo}, where allow_update_branch is already documented. The work is done when the property appears in the POST request body and the provided gh api commands still produce true and false as expected.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

The POST /user/repos endpoint does not list the property allow_update_branch in the request body, however it can be used to set this repository setting on creation.

The allow_update_branch request body property can be seen in the PATCH /repos/{owner}/{repo} endpoint.

Expected

The allow_update_branch property should be listed in the request body of POST /user/repos.

Reproduction Steps

Create two repositories and print the value of allow_update_branch of the created repositories:

$ gh api -X POST /user/repos -f name=test_allow_update_branch_1 -f allow_update_branch=true -q .allow_update_branch
true
$ gh api -X POST /user/repos -f name=test_allow_update_branch_2 -f allow_update_branch=false -q .allow_update_branch
false

Dominant language: No language data
Stars: 1.6k
Forks: 342
Avg merge: 3h 33m
Merged PRs (30d): 51

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug]: Matrix progress drafts fail with "Matrix runtime not initialized" during tool activity Open

bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

openclaw/openclaw#155298 · 2 comments · 1 reaction · Opened Sep 22, 2026
[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
MCP client has no httpx timeout, so the event stream fails after 5 seconds Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Azure/azure-functions-agents-runtime#228 · Opened Sep 21, 2026
feat(mcp): friendlier error when `run_cloud_sync` is called on a disabled connection Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

airbytehq/PyAirbyte#1205 · Opened Sep 21, 2026

More Backend & API Design issues