[Schema Inaccuracy] Example and schema mismatch for `#/paths/~1orgs~1{org}~1code-security~1configurations~1defaults/get`
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- openapi
- Domain
- api
Research direction
Start by comparing the schema for #/paths/1orgs1{org}1code-security1configurations~1defaults/get with the example at #/components/examples/code-security-default-configurations/value. Check how security_configuration_id is represented in each, then verify that the schema and example are in sync for the reported GHES 3.15 case.
Written by the indexing model from the issue text.
Description
Schema Inaccuracy
This is the json ref for the example
#/components/examples/code-security-default-configurations/value
The field security_configuration_id doesn't exist in the schema, but exists in the example.
Here's a snippet
14: "secret_scanning_push_protection" : "enabled",
15: "secret_scanning_delegated_bypass" : "enabled",
16: "secret_scanning_delegated_bypass_options" : {
17: "reviewers" : [ {
> 18: "security_configuration_id" : 1325,
19: "reviewer_id" : 5678,
20: "reviewer_type" : "TEAM"
21: } ]
22: },
Expected
The schema and example are in sync
Reproduction Steps
I could reproduce this in
- ghes-3.15
- Dominant language
- No language data
- Stars
- 1.6k
- Forks
- 342
- Avg merge
- 3h 33m
- Merged PRs (30d)
- 51
Contributor 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.
More from github/rest-api-description
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/rest-api-description#7201 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/rest-api-description#7163 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7162 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7135 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
github/rest-api-description#7111 · 1 comment ·
All issues in github/rest-api-description
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#165 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100