Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Schema Inaccuracy] Example and schema mismatch for `#/paths/~1installation~1repositories/get`

Open
#5,497 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
Clearly specified
Activity status
Stale
Tech stack
openapi
Domain
api

Research direction

Start by comparing the schema for #/paths/1installation1repositories/get with the example at #/components/examples/repository-paginated-2/value. Check how template_repository is represented in each, then update the mismatched schema or example so they agree and verify the endpoint description remains valid.

Written by the indexing model from the issue text.

Description

content documentation

Schema Inaccuracy

This is the json ref for the example

#/components/examples/repository-paginated-2/value

The field template_repository doesn't exist in the schema, but exists in the example.

Here's a snippet

   91:     "pushed_at" : "2011-01-26T19:06:43Z",
   92:     "created_at" : "2011-01-26T19:01:12Z",
   93:     "updated_at" : "2011-01-26T19:14:43Z",
   94:     "allow_rebase_merge" : true,
>  95:     "template_repository" : null,
   96:     "temp_clone_token" : "ABTLWHOULUVAXGTRYU7OC2876QJ2O",
   97:     "allow_squash_merge" : true,
   98:     "allow_auto_merge" : false,
   99:     "delete_branch_on_merge" : true,

Expected

The schema and example are in sync

Reproduction Steps

I could reproduce this in

  • fpt
  • ghec
  • ghes-3.14
  • ghes-3.15
  • ghes-3.16
  • ghes-3.17
Dominant language
No language data
Stars
1.6k
Forks
342
Avg merge
2h 23m
Merged PRs (30d)
57

Contributor guide

Open the contributing guide

First steps

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

More from github/rest-api-description

All issues in github/rest-api-description

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.