Skip to content

Commit 066dbf5

Browse files
authored
Merge pull request #3979 from github/openapi-update-24266c733ba431ba90c118f34658c845c1dd4ddc9eacba4d5073db8dcd6cd953
Update OpenAPI 3.1 Descriptions
2 parents 5b5fba4 + 36bc4aa commit 066dbf5

16 files changed

+24
-24
lines changed

descriptions-next/api.github.com/api.github.com.2022-11-28.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26942,7 +26942,7 @@
2694226942
"/repos/{owner}/{repo}/attestations": {
2694326943
"post": {
2694426944
"summary": "Create an attestation",
26945-
"description": "Store an artifact attestation and associate it with a repository.\n\nThe authenticated user must have write permission to the repository and, if using a fine-grained access token the `attestations:write` permission is required.\n\nArtifact attestations are meant to be created using the [attest action](https://github.com/actions/attest). For amore information, see our guide on [using artifact attestations to establish a build's provenance](https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).",
26945+
"description": "Store an artifact attestation and associate it with a repository.\n\nThe authenticated user must have write permission to the repository and, if using a fine-grained access token, the `attestations:write` permission is required.\n\nArtifact attestations are meant to be created using the [attest action](https://github.com/actions/attest). For more information, see our guide on [using artifact attestations to establish a build's provenance](https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).",
2694626946
"tags": [
2694726947
"repos"
2694826948
],

descriptions-next/api.github.com/api.github.com.2022-11-28.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19498,9 +19498,9 @@ paths:
1949819498
description: |-
1949919499
Store an artifact attestation and associate it with a repository.
1950019500

19501-
The authenticated user must have write permission to the repository and, if using a fine-grained access token the `attestations:write` permission is required.
19501+
The authenticated user must have write permission to the repository and, if using a fine-grained access token, the `attestations:write` permission is required.
1950219502

19503-
Artifact attestations are meant to be created using the [attest action](https://github.com/actions/attest). For amore information, see our guide on [using artifact attestations to establish a build's provenance](https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
19503+
Artifact attestations are meant to be created using the [attest action](https://github.com/actions/attest). For more information, see our guide on [using artifact attestations to establish a build's provenance](https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
1950419504
tags:
1950519505
- repos
1950619506
operationId: repos/create-attestation

0 commit comments

Comments
 (0)