From ced20bab7d8c317a05823ebe804a51bc741cdad8 Mon Sep 17 00:00:00 2001 From: Mike Mwanje <41787587+123MwanjeMike@users.noreply.github.com> Date: Sat, 10 Jul 2021 17:42:24 +0300 Subject: [PATCH 1/3] Update migrating-oauth-apps-to-github-apps.md These changes are to include the 'Delete OAuth App' step in 'Migrating OAuth Apps to GitHub Apps' --- .../migrating-oauth-apps-to-github-apps.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md b/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md index 408e854582..a450696f00 100644 --- a/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md +++ b/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md @@ -40,7 +40,8 @@ These guidelines assume that you have a registered OAuth App{% ifversion fpt %} 1. [Understand the different methods of authentication](#understand-the-different-methods-of-authentication) 1. [Direct users to install your GitHub App on repositories](#direct-users-to-install-your-github-app-on-repositories) 1. [Remove any unnecessary repository hooks](#remove-any-unnecessary-repository-hooks) -1. [Encourage users to revoke access to your OAuth app](#encourage-users-to-revoke-access-to-your-oauth-app) +1. [Encourage users to revoke access to your OAuth App](#encourage-users-to-revoke-access-to-your-oauth-app) +1. [Delete the OAuth App](#delete-the-oauth-app) ### Review the available API endpoints for GitHub Apps @@ -100,4 +101,8 @@ Once your GitHub App has been installed on a repository, you should remove any u ### Encourage users to revoke access to your OAuth app -As your GitHub App installation base grows, consider encouraging your users to revoke access to the legacy OAuth integration. For more information, see [Authorizing OAuth Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) +As your GitHub App installation base grows, consider encouraging your users to revoke access to the legacy OAuth integration. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)." + +### Delete the OAuth App + +To avoid abuse of the OAuth App's credentials, consider deleting the OAuth App. This action will also revoke all of the OAuth App's remaining authorizations. For more information, see "[Deleting an OAuth App](/developers/apps/managing-oauth-apps/deleting-an-oauth-app)." From 9a0cb726ad555efd7448d91d17b8fba0d00fe217 Mon Sep 17 00:00:00 2001 From: blue-jam Date: Wed, 4 May 2022 09:04:51 +0900 Subject: [PATCH 2/3] Typo: make container name consistent --- .../working-with-the-container-registry.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md index 48ed86228b..19ce6bdeba 100644 --- a/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md +++ b/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md @@ -35,14 +35,14 @@ When installing or publishing a Docker image, the {% data variables.product.prod ## Pushing container images -This example pushes the latest version of `IMAGE-NAME`. +This example pushes the latest version of `IMAGE_NAME`. ```shell $ docker push ghcr.io/OWNER/IMAGE_NAME:latest ``` This example pushes the `2.5` version of the image. ```shell - $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5 + $ docker push ghcr.io/OWNER/IMAGE_NAME:2.5 ``` When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." From 256e5d0e3d5b944130057d426cb23091358a9396 Mon Sep 17 00:00:00 2001 From: Christos Karampatzakis <63047451+ckarampa@users.noreply.github.com> Date: Thu, 12 May 2022 10:56:40 +0300 Subject: [PATCH 3/3] Typo in adding upstream repository. --- content/get-started/quickstart/fork-a-repo.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/get-started/quickstart/fork-a-repo.md b/content/get-started/quickstart/fork-a-repo.md index 4f88dbce63..08dad271e6 100644 --- a/content/get-started/quickstart/fork-a-repo.md +++ b/content/get-started/quickstart/fork-a-repo.md @@ -154,7 +154,7 @@ When you fork a project in order to propose changes to the original repository, 6. Type `git remote add upstream`, and then paste the URL you copied in Step 3 and press **Enter**. It will look like this: ```shell - $ git remote add upstream https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/Spoon-Knife.git + $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git ``` 7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.