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

[Schema Inaccuracy] Several fields in `auto_merge` should be nullable

Open
#5,564 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
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
openapi
Domain
api

Research direction

Inspect the OpenAPI schema definitions for the auto_merge fields used by the pull-request create and fetch APIs, then compare them with the reproduction response at https://api.github.com/repos/javaparser/javaparser/pulls/4565. Done means the fields that can be null are marked nullable in the relevant schemas and the affected API descriptions remain valid.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

Several APIs related to creating/fetching PRs have an auto_merge key which provides information about how auto merge is configured.

Expected

These fields are actually nullable but are not marked as such

Reproduction Steps

https://api.github.com/repos/javaparser/javaparser/pulls/4565

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.