You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub [recently started verifying GPG signed commits and tags](https://github.com/blog/2144-gpg-signature-verification). We are adding API support for signature verification and user GPG key management as well. You can enable these changes during the preview period by providing a custom [media type][media-type] in the `Accept` header:
You can learn more about the new signature verification response objects in the updated [repository commit][repo-commit-doc], [Git commit][git-commit-doc], and [Git tag][git-tag-doc] documentation. There is also new [GPG key management][gpg-keys-doc] documentation.
19
+
20
+
During the preview period, we may change aspects of these APIs based on developer feedback. We will announce the changes here on the developer blog, but we will not provide advance notice.
21
+
22
+
If you have any questions or feedback, please [let us know][contact].
Copy file name to clipboardExpand all lines: content/v3/repos/commits.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,3 +95,28 @@ Pass the appropriate [media type](/v3/media/#commits-commit-comparison-and-pull-
95
95
The response will include a comparison of up to 250 commits. If you are working with a larger commit range, you can use the [Commit List API](/v3/repos/commits/#list-commits-on-a-repository) to enumerate all commits in the range.
96
96
97
97
For comparisons with extremely large diffs, you may receive an error response indicating that the diff took too long to generate. You can typically resolve this error by using a smaller commit range.
98
+
99
+
{% if page.version == 'dotcom' %}
100
+
101
+
## Commit signature verification
102
+
103
+
{{#tip}}
104
+
105
+
Commit response objects including signature verification data are currently available for developers to preview.
106
+
During the preview period, the object formats may change without advance notice.
107
+
Please see the [blog post](/changes/2016-04-04-git-signing-api-preview) for full details.
108
+
109
+
To receive signature verification data in commit objects you must provide a custom [media type](/v3/media) in the `Accept` header:
0 commit comments