Confusing Header in code-samples for `Create a GitHub App from a manifest`

[HiteshMah-Jan]

Schema Inaccuracy

The "Code Samples" widget at Create a GitHub App from a manifest shows an extra Authorization Header under samples for cURL and JavaScript.
Adding an auth token in place of YOUR-TOKEN does work, but for the API to work it is not required. The documentation does not state/describe the Authorization Header, thus leaves developers to wonder what value is needed to be passed in it.

Expected

The Authorization Header in this code sample needs to be removed or ignored in the API itself. The API should not raise a 401 status if an incorrect header is passed.

Reproduction Steps

1. Generate a temporary code using a Github App manifest
2. Use this code in the cURL call copied from Github Rest Documentation for Create a GitHub App from a manifest

curl \
  -X POST \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <YOUR-TOKEN>" \
  https://api.github.com/app-manifests/<code-from-step-2>/conversions

[nickfloyd]

Please let us know if this work is still needed. We're trying to follow up on any older issues to make sure they get properly routed.