[Schema Inaccuracy] schema `content-directory` should have enum limited to `dir` value in gh-3.18

Open

#5,571 opened on Nov 5, 2025 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 1/5
Estimated time: Under an hour
Newbie friendliness: 50/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Stale
Tech stack: openapi, yaml
Domain: api

Research direction

Read the gh-3.18 schema at the linked gh.yaml URL and locate the content-directory definition. Compare its type enum with the Expected block, then verify the schema contains only the intended value. Done means the gh-3.18 description reflects the requested enum restriction.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

In the latest version of gh.yaml (3.18) the type content-directory has an incorrect type property.

    content-directory:
      title: Content Directory
      description: A list of directory items
      type: array
      items:
        type: object
        properties:
          type:
            type: string
            enum:
            - dir
            - file
            - submodule
            - symlink
...

Expected

    content-directory:
      title: Content Directory
      description: A list of directory items
      type: array
      items:
        type: object
        properties:
          type:
            type: string
            enum:
            - dir
...

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