[Schema Inaccuracy] Invalid example for /repos/{owner}/{repo}/issues/{issue_number}

Open

#5,234 opened on Aug 15, 2025 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: openapi
Domain: api

Research direction

Start by locating the PATCH request body at the provided OpenAPI path and compare its schema with the default example. Remove or reconcile the unexpected issue_field_values field so the schema and example are in sync, then verify the resulting description against the reported reproduction targets.

Written by the indexing model from the issue text.

Description

documentation

Schema Inaccuracy

The example contains an unexpected field issue_field_values that the schema doesn't.
The example is at #/paths/~1repos~1{owner}~1{repo}~1issues~1{issue_number}/patch/requestBody/content/application~1json/examples/default/value
The schema is at #/paths/~1repos~1{owner}~1{repo}~1issues~1{issue_number}/patch/requestBody/content/application~1json/schema.

            1: {
            2:   "assignees" : [ "octocat" ],
            3:   "body" : "I'm having a problem with this.",
        >   4:   "issue_field_values" : [ {
            5:     "field_id" : "123",
            6:     "value" : "Critical"
            7:   }, {
            8:     "field_id" : "456",

Expected

The schema and example are in sync

Reproduction Steps

I found this in
- ghec
- fpt
- ghes-3.14
- ghes-3.15
- ghes-3.16
- ghes-3.17

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] @mastra/inngest: errors thrown inside durable steps lose their original stack (and error type) — Inngest only sees the wrapper frame Open

bug customer-eng Durable Agents Inngest status: needs triage

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

mastra-ai/mastra#24748 · 1 comment · Opened Sep 22, 2026
[Bug report] iceberg rest server load_table with refs fails precondition check "Cannot set metadata location with changes to table metadata: %s changes" for snapshots with statistics Open

bug

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

apache/gravitino#13452 · Opened Sep 22, 2026
ElevenLabs: only first sentence spoken with eleven_v3_conversational (previous_request_ids not supported) Open

integration: elevenlabs

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

home-assistant/core#182944 · 1 comment · Opened Sep 22, 2026
bug report: ai observability - dry-running a paused evaluation emails the whole org Open

ai-observability bug team/ai-observability

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

PostHog/posthog#104687 · Opened Sep 22, 2026
Dev server : any request to a nonexistent /api/* path hangs indefinitely Open

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

vicharanashala/fln#563 · Opened Sep 22, 2026

More Backend & API Design issues