From 00d01aa96f6277e6a0d3c81f3d1ea8bd169a3963 Mon Sep 17 00:00:00 2001 From: Julian Joseph Date: Tue, 10 Nov 2020 15:46:22 -0800 Subject: [PATCH 1/3] Added filter out documentation using `-` --- .../using-search-to-filter-issues-and-pull-requests.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index fcb3518947a6..4b978b4222bb 100644 --- a/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -25,6 +25,7 @@ With issue and pull request search terms, you can: - Filter issues and pull requests that involve, but don't necessarily [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), certain people: `state:open type:issue involves:octocat` - Filter issues and pull requests by assignee: `state:open type:issue assignee:octocat` - Filter issues and pull requests by label: `state:open type:issue label:"bug"` +- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} For issues, you can also use search to: From 16d697680d1375848675be5f3b3c66604307b90b Mon Sep 17 00:00:00 2001 From: Guilherme Macedo Date: Wed, 18 Nov 2020 00:25:39 +0100 Subject: [PATCH 2/3] Update authenticating-with-github-apps.md Fix small typo. --- content/developers/apps/authenticating-with-github-apps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/developers/apps/authenticating-with-github-apps.md b/content/developers/apps/authenticating-with-github-apps.md index 3e6cb121759f..d839a6713177 100644 --- a/content/developers/apps/authenticating-with-github-apps.md +++ b/content/developers/apps/authenticating-with-github-apps.md @@ -28,7 +28,7 @@ To generate a private key: {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -5. In "Private keys," click **Generate a private key**. +5. In "Private keys", click **Generate a private key**. ![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png) 6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key. From 5c2ef0fa4c73d1223ff97d039a0b66139c15b5eb Mon Sep 17 00:00:00 2001 From: Jamie Cansdale Date: Wed, 25 Nov 2020 11:45:55 +0000 Subject: [PATCH 3/3] Don't specify registry specific path --- data/reusables/package_registry/authenticate-packages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/package_registry/authenticate-packages.md b/data/reusables/package_registry/authenticate-packages.md index 11de4d874fa7..64b208d748c9 100644 --- a/data/reusables/package_registry/authenticate-packages.md +++ b/data/reusables/package_registry/authenticate-packages.md @@ -2,7 +2,7 @@ You need an access token to publish, install, and delete packages. You can use a {% if currentVersion == "free-pro-team@latest" %} To authenticate using a {% data variables.product.prodname_actions %} workflow: -- For package registries (`PACKAGE-REGISTRY.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`), you can use a `GITHUB_TOKEN`. +- For package registries (`PACKAGE-REGISTRY.pkg.github.com`), you can use a `GITHUB_TOKEN`. - For the container registry (`ghcr.io/OWNER/IMAGE-NAME`), you must use a personal access token. {% else %} To authenticate to {% data variables.product.prodname_registry %} using a {% data variables.product.prodname_actions %} workflow, you must use `GITHUB_TOKEN`.