This repository has been archived by the owner on Nov 1, 2017. It is now read-only.
GPG Keys documentation specify multiple potential Accept values #1074
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shiftkey
force-pushed
the
shiftkey-correct-media-type
branch
from
84bb8fa to
3f40d00
Compare
|
Looks good to me 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@alfhenrik pointed out over in this issue that the preview headers for GPG Keys are not consistent:
application/vnd.github.cryptographer-previewas per the announcement blog postapplication/vnd.github.cryptographer-preview+shaas per the current docsI tested both values with a valid token and they fine, but this PR normalizes the docs to use
application/vnd.github.cryptographer-previewto be consistent with most of our other preview APIs.Let me know if anything is unclear here.