[Schema Inaccuracy] api.github.com webhooks contains `enterprise` key in `descriptions-next`

Open
#1,751 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
openapi
Domain
api

Research direction

Inspect the api.github.com OpenAPI spec in the descriptions-next version, focusing on webhook definitions that include the enterprise key. Compare those definitions with the api.github.com scope described in the issue. Done means the enterprise key is absent from the api.github.com webhook schemas while remaining scope-specific elsewhere.

Written by the indexing model from the issue text.

Description

inaccuracy P4

Schema Inaccuracy

In the OpenAPI spec for api.github.com there are many instances of webhooks that contain the enterprise key.
That key doesn't exist in the api.github.com scope.

Expected

For there not to be an enterprise key within the api.github.com spec

Reproduction Steps

N/A

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

  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.