[Schema Bug] Multiple different endpoints are using the same value for `operationID` GHES 3.12, GHES 3.13

[wolfy1339]

Schema Inaccuracy

Multiple different endpoints are using the same value for operationID of enterprise-admin/get-manage-settings

• GET /manage/v1/config/apply/events
• GET /manage/v1/config/settings
• GET /manage/v1/config/apply
• POST /manage/v1/config/apply

Expected

Each endpoint has it's own uniuqe operationID The the OpenAPI specs be free of bugs like this one that prevents it's usage

Reproduction Steps

N/A as it concerns the schema definitions and not actual response data

Suggested solution

I would like to suggest that the OpenAPI specs be passed through a linter of the likes of Redocly before publishing to minimize any bugs like this

See https://github.com/octokit/openapi-types.ts/pull/429#issuecomment-2209656935

[shiftkey]

@wolfy1339 thanks for the heads up - I've reached out to the team who created these operations, shouldn't be too hard to fix.

[Just091]

Bcp14

[Just091]

BCP14