Skip to content

Commit ca85f1b

Browse files
authored
Merge pull request #17579 from github/repo-sync
repo sync
2 parents 37a65d7 + 6788a13 commit ca85f1b

25 files changed

+131
-47
lines changed

content/rest/apps/apps.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
2-
title: Apps
3-
intro: 'The GitHub Apps API enables you to retrieve the information about the installation as well as specific information about GitHub Apps.'
2+
title: GitHub Apps
3+
allowTitleToDifferFromFilename: true
4+
intro: 'The {% data variables.product.prodname_github_apps %} API enables you to retrieve information about {% data variables.product.prodname_github_apps %}.'
45
topics:
56
- API
67
miniTocMaxHeadingLevel: 3
@@ -11,12 +12,14 @@ versions:
1112
ghec: '*'
1213
---
1314

15+
## About the {% data variables.product.prodname_github_apps %} API
16+
1417
{% data reusables.apps.general-apps-restrictions %}
1518

1619
This page lists endpoints that you can access while authenticated as a GitHub App. See "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" to learn more.
1720

1821
When authenticated as a GitHub App, the GitHub Apps API enables you to get high-level information about a GitHub App as well as specific information about installations of an app.
1922

20-
You can access REST API v3 endpoints while authenticated as a GitHub App. These endpoints have a "Notes" section that contains a bullet point that says "Works with GitHub Apps." You can also access these endpoints while authenticated as a user.
23+
You can access REST API v3 endpoints while authenticated as a GitHub App. These endpoints have text that says "Works with GitHub Apps." You can also access these endpoints while authenticated as a user.
2124

2225
A subset of REST API v3 endpoints requires authenticating as a GitHub App installation. See [Installations](/rest/reference/apps#installations) for a list of these endpoints.

content/rest/apps/installations.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
2-
title: Installations
3-
intro: 'The Installations API enables you to get information about installations of your GitHub App and perform actions within those installations.'
2+
title: GitHub App installations
3+
allowTitleToDifferFromFilename: true
4+
shortTitle: Installations
5+
intro: 'The {% data variables.product.prodname_github_app %} installations API enables you to get information about installations of your {% data variables.product.prodname_github_app %} and perform actions within those installations.'
46
topics:
57
- API
68
miniTocMaxHeadingLevel: 3
@@ -11,6 +13,8 @@ versions:
1113
ghec: '*'
1214
---
1315

16+
## About the {% data variables.product.prodname_github_app %} installations API
17+
1418
An _installation_ refers to any user or organization account that has installed the app. For information on how to authenticate as an installation and limit access to specific repositories, see "[Authenticating as an installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
1519

1620
To list all GitHub App installations for an organization, see "[List app installations for an organization](/rest/reference/orgs#list-app-installations-for-an-organization)."

content/rest/apps/marketplace.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
---
2-
title: Marketplace
2+
title: GitHub Marketplace
3+
allowTitleToDifferFromFilename: true
4+
shortTitle: Marketplace
35
intro: ''
46
topics:
57
- API
@@ -9,6 +11,8 @@ versions:
911
ghec: '*'
1012
---
1113

14+
## About the {% data variables.product.prodname_marketplace %} API
15+
1216
For more information about {% data variables.product.prodname_marketplace %}, see "[GitHub Marketplace](/marketplace/)."
1317

1418
The {% data variables.product.prodname_marketplace %} API allows you to see which customers are using a pricing plan, see a customer's purchases, and see if an account has an active subscription.

content/rest/apps/oauth-applications.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
title: OAuth Applications
2+
title: OAuth Apps
3+
allowTitleToDifferFromFilename: true
34
intro: ''
45
topics:
56
- API
@@ -11,4 +12,6 @@ versions:
1112
ghec: '*'
1213
---
1314

14-
You can use this API to manage the OAuth tokens an OAuth application uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
15+
## About the {% data variables.product.prodname_oauth_app %} API
16+
17+
You can use this API to manage the OAuth tokens an {% data variables.product.prodname_oauth_app %} uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.

content/rest/apps/webhooks.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
---
2-
title: Webhooks
2+
title: GitHub App webhooks
3+
allowTitleToDifferFromFilename: true
4+
shortTitle: Webhooks
35
intro: ''
46
topics:
57
- API
@@ -11,4 +13,6 @@ versions:
1113
ghec: '*'
1214
---
1315

16+
## About the {% data variables.product.prodname_github_app %} webhooks API
17+
1418
A {% data variables.product.prodname_github_app %}'s webhook allows you to receive HTTP `POST` payloads whenever certain events happen for an app. {% data reusables.webhooks.webhooks-rest-api-links %}

content/rest/codespaces/codespaces.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,4 +11,6 @@ miniTocMaxHeadingLevel: 3
1111

1212
{% data reusables.codespaces.codespaces-api-beta-note %}
1313

14+
## About the Codespaces API
15+
1416
The {% data variables.product.prodname_codespaces %} API enables you to manage {% data variables.product.prodname_codespaces %} using the REST API. This API is available for authenticated users and OAuth Apps, but not GitHub Apps. For more information, see "[{% data variables.product.prodname_codespaces %}](/codespaces)."

content/rest/codespaces/machines.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
2-
title: Machines
3-
intro: 'The Machines API allows a user to determine which machine types are available to create a codespace, either on a given repository or as an authenticated user.'
2+
title: Codespaces machines
3+
allowTitleToDifferFromFilename: true
4+
shortTitle: Machines
5+
intro: 'The Codespaces machines API allows a user to determine which machine types are available to create a codespace, either on a given repository or as an authenticated user.'
46
versions:
57
fpt: '*'
68
ghec: '*'
@@ -9,6 +11,8 @@ topics:
911
miniTocMaxHeadingLevel: 3
1012
---
1113

12-
For more information, see "[About machine types](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)."
14+
## About the Codespaces machines API
15+
16+
The Codespaces machines API allows a user to determine which machine types are available to create a codespace, either on a given repository or as an authenticated user. For more information, see "[About machine types](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)."
1317

1418
You can also use this information when changing the machine of an existing codespace by updating its `machine` property. The machine update will take place the next time the codespace is restarted. For more information, see "[Changing the machine type for your codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)."
Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
2-
title: Repository Secrets
3-
intro: 'The Repository Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) for repositories that the user has access to.'
2+
title: Codespaces repository secrets
3+
allowTitleToDifferFromFilename: true
4+
shortTitle: Repository secrets
5+
intro: 'The Codespaces repository secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) for repositories that the user has access to in a codespace.'
46
versions:
57
fpt: '*'
68
ghec: '*'
@@ -10,6 +12,6 @@ topics:
1012
miniTocMaxHeadingLevel: 3
1113
---
1214

13-
## Repository Secrets
15+
## About the Codespaces repository secrets API
1416

15-
The Repository Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) for repositories that the user has access to. These secrets are made available to the codespace at runtime. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
17+
The Codespaces repository secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) for repositories that the user has access to. These secrets are made available to the codespace at runtime. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."

content/rest/codespaces/secrets.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,16 @@
11
---
2-
title: User Secrets
3-
intro: 'The User Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to.'
2+
title: Codespaces user secrets
3+
allowTitleToDifferFromFilename: true
4+
shortTitle: User secrets
5+
intro: 'The Codespaces user secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to in a codespace.'
46
versions:
57
fpt: '*'
68
ghec: '*'
79
topics:
810
- API
911
miniTocMaxHeadingLevel: 3
10-
allowTitleToDifferFromFilename: true
1112
---
1213

13-
## User Secrets
14+
## About the Codespaces user secrets API
1415

15-
The User Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to. These secrets are made available to the codespace at runtime. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
16+
The Codespaces user secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to. These secrets are made available to the codespace at runtime. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."

content/rest/deployments/deployments.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ topics:
1111
miniTocMaxHeadingLevel: 3
1212
---
1313

14+
## About the deployments API
15+
1416
Deployments are requests to deploy a specific ref (branch, SHA, tag). GitHub dispatches a [`deployment` event](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) that external services can listen for and act on when new deployments are created. Deployments enable developers and organizations to build loosely coupled tooling around deployments, without having to worry about the implementation details of delivering different types of applications (e.g., web, native).
1517

1618
Deployment statuses allow external services to mark deployments with an `error`, `failure`, `pending`, `in_progress`, `queued`, or `success` state that systems listening to [`deployment_status` events](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) can consume.

0 commit comments

Comments
 (0)