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
Copy file name to clipboardExpand all lines: content/developers/apps/creating-ci-tests-with-the-checks-api.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ versions:
12
12
13
13
### Introduction
14
14
15
-
This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests.
15
+
This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests.
16
16
17
17
CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts. 🙌
18
18
@@ -49,7 +49,7 @@ To get an idea of what your Checks API CI server will do when you've completed t
49
49
50
50
### Prerequisites
51
51
52
-
Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details.
52
+
Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details.
53
53
54
54
You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app.
55
55
@@ -203,7 +203,7 @@ Great! You've told GitHub to create a check run. You can see the check run statu
203
203
204
204
### Step 1.4. Updating a check run
205
205
206
-
When your `create_check_run` method runs, it asks GitHub to create a new check run. When Github finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check.
206
+
When your `create_check_run` method runs, it asks GitHub to create a new check run. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check.
207
207
208
208
You'll want to update your event handler to look for the `created` action. While you're updating the event handler, you can add a conditional for the `rerequested` action. When someone re-runs a single test on GitHub by clicking the "Re-run" button, GitHub sends the `rerequested` check run event to your app. When a check run is `rerequested`, you'll want to start the process all over and create a new check run.
Copy file name to clipboardExpand all lines: content/developers/apps/migrating-oauth-apps-to-github-apps.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/under
52
52
53
53
#### Register a new GitHub App
54
54
55
-
Once you've decided to make the switch to Github Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/).
55
+
Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/).
56
56
57
57
#### Determine the permissions your app requires
58
58
@@ -62,7 +62,7 @@ In your GitHub App's settings, you can specify whether your app needs `No Access
62
62
63
63
#### Subscribe to webhooks
64
64
65
-
After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a Github App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks.
65
+
After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks.
66
66
67
67
#### Understand the different methods of authentication
Copy file name to clipboardExpand all lines: content/developers/github-marketplace/handling-new-purchases-and-free-trials.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ See "[{% data variables.product.prodname_marketplace %} webhook events](/marketp
36
36
37
37
If your app is a GitHub App, GitHub prompts the customer to select which repositories the app can access when they purchase it. GitHub then installs the app on the account the customer selected and grants access to the selected repositories.
38
38
39
-
At this point, if you specified a **Setup URL** in your GitHub App settings, Github will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your GitHub App.
39
+
At this point, if you specified a **Setup URL** in your GitHub App settings, GitHub will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your GitHub App.
Copy file name to clipboardExpand all lines: content/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ After you enable SCIM, the following provisioning features are available for any
31
31
{% data reusables.saml.okta-dashboard-click-applications %}
32
32
{% data reusables.saml.add-okta-application %}
33
33
{% data reusables.saml.search-ghec-okta %}
34
-
4. To the right of "Github Enterprise Cloud - Organization", click **Add**.
34
+
4. To the right of "GitHub Enterprise Cloud - Organization", click **Add**.
35
35
36
36
37
37
5. In the **GitHub Organization** field, type the name of your {% data variables.product.prodname_dotcom %} organization. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`.
@@ -57,16 +57,16 @@ After you enable SCIM, the following provisioning features are available for any
57
57
{% data reusables.saml.okta-enable-api-integration %}
58
58
59
59
60
-
6. Click **Authenticate with Github Enterprise Cloud - Organization**.
61
-
60
+
6. Click **Authenticate with GitHub Enterprise Cloud - Organization**.
61
+
62
62
63
63
7. To the right of your organization's name, click **Grant**.
64
64
65
65
66
66
{% note %}
67
-
67
+
68
68
**Note**: If you don't see your organization in the list, go to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser and authenticate with your organization via SAML SSO using your administrator account on the IdP. For example, if your organization's name is `octo-org`, the URL would be `https://github.com/orgs/octo-org/sso`. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
69
-
69
+
70
70
{% endnote %}
71
71
1. Click **Authorize OktaOAN**.
72
72
Copy file name to clipboardExpand all lines: content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ To configure user provisioning with SCIM in Okta, you must authorize an OAuth ap
76
76
{% data reusables.saml.okta-provisioning-tab %}
77
77
{% data reusables.saml.okta-configure-api-integration %}
78
78
{% data reusables.saml.okta-enable-api-integration %}
79
-
1. Click **Authenticate with Github Enterprise Cloud - Enterprise Accounts**.
79
+
1. Click **Authenticate with GitHub Enterprise Cloud - Enterprise Accounts**.
80
80
81
81
1. To the right of your enterprise account's name, click **Grant**.
0 commit comments