From 8b6a02bc1ff7cd833e7ef92299970af48ee59c28 Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Mon, 16 Aug 2021 17:55:47 +0200 Subject: [PATCH 1/8] clarify limitations of project board visibility settings --- .../changing-project-board-visibility.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md index 2b0d4dc68a..f8ddceece1 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: Changing project board visibility -intro: 'As an organization owner or project board admin, you can make a project board {% ifversion ghae %}internal{% else %}public{% endif %} or private.' +intro: 'Account owners and project board admins can make their user owned or organization owned project boards {% ifversion ghae %}internal{% else %}public{% endif %} or private. Repository owned project boards inherit their visibility from the owning repository.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility - /articles/changing-project-board-visibility @@ -19,7 +19,7 @@ shortTitle: Change visibility {% tip %} -**Tip:** When you make your project board {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Tip:** When you make your organization owned project board {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endtip %} From 8d01eef3ebfe99bffc039c97a47cdf6d9e2665ed Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Mon, 23 Aug 2021 15:26:04 +0200 Subject: [PATCH 2/8] created PR search reusable and added to relevent docs --- .../using-search-to-filter-issues-and-pull-requests.md | 8 ++++++++ .../searching-issues-and-pull-requests.md | 6 ++++++ data/reusables/pull_requests/large-search-workaround.md | 1 + 3 files changed, 15 insertions(+) create mode 100644 data/reusables/pull_requests/large-search-workaround.md diff --git a/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md b/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md index 043f3b298a..8a73915e10 100644 --- a/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md +++ b/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md @@ -58,6 +58,14 @@ For pull requests, you can also use search to: - Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae %} - Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`{% endif %} +{% note %} + +**Note:** {% data reusables.pull_requests.large-search-workaround %} You can do this by adding the `org:`, `user:`, or `repo:` qualifier to your search. + +{% endnote %} + + + ## Further reading - "[Searching issues and pull requests](/articles/searching-issues)" diff --git a/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md b/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md index 37e428b9f0..9b3c7f569d 100644 --- a/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md @@ -56,6 +56,12 @@ To search issues and pull requests in all repositories owned by a certain user o | org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) matches issues in repositories owned by the GitHub organization. | repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) matches issues from @mozilla's shumway project that were created before March 2012. +{% note %} + +**Note:** {% data reusables.pull_requests.large-search-workaround %} + +{% endnote %} + ## Search by open or closed state You can filter issues and pull requests based on whether they're open or closed using the `state` or `is` qualifier. diff --git a/data/reusables/pull_requests/large-search-workaround.md b/data/reusables/pull_requests/large-search-workaround.md new file mode 100644 index 0000000000..bc3a0d16f9 --- /dev/null +++ b/data/reusables/pull_requests/large-search-workaround.md @@ -0,0 +1 @@ +If you have access to 10,000+ pull requests, you will need to limit your search to a specific organization, user account, or repository in order to see accurate results. \ No newline at end of file From 84aba0b84c5b09526324d30cd4c839d843cdc1c5 Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Tue, 24 Aug 2021 09:32:37 +0200 Subject: [PATCH 3/8] Revert "clarify limitations of project board visibility settings" This reverts commit 8b6a02bc1ff7cd833e7ef92299970af48ee59c28. --- .../changing-project-board-visibility.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md index f8ddceece1..2b0d4dc68a 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: Changing project board visibility -intro: 'Account owners and project board admins can make their user owned or organization owned project boards {% ifversion ghae %}internal{% else %}public{% endif %} or private. Repository owned project boards inherit their visibility from the owning repository.' +intro: 'As an organization owner or project board admin, you can make a project board {% ifversion ghae %}internal{% else %}public{% endif %} or private.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility - /articles/changing-project-board-visibility @@ -19,7 +19,7 @@ shortTitle: Change visibility {% tip %} -**Tip:** When you make your organization owned project board {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Tip:** When you make your project board {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endtip %} From b82d28a7e2bd76c2c0837cc137623760c47be976 Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Tue, 24 Aug 2021 12:48:17 +0200 Subject: [PATCH 4/8] Update data/reusables/pull_requests/large-search-workaround.md Co-authored-by: Matt Pollard --- data/reusables/pull_requests/large-search-workaround.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/pull_requests/large-search-workaround.md b/data/reusables/pull_requests/large-search-workaround.md index bc3a0d16f9..c0e68b6b9b 100644 --- a/data/reusables/pull_requests/large-search-workaround.md +++ b/data/reusables/pull_requests/large-search-workaround.md @@ -1 +1 @@ -If you have access to 10,000+ pull requests, you will need to limit your search to a specific organization, user account, or repository in order to see accurate results. \ No newline at end of file +If you have access to pull requests in more than 10,000 repositories, you will need to limit your search to a specific organization, user account, or repository to see results. \ No newline at end of file From 31aca7451861204547d2906db03564f80ebeb4b0 Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Tue, 24 Aug 2021 12:49:21 +0200 Subject: [PATCH 5/8] Update content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md Co-authored-by: Matt Pollard --- .../using-search-to-filter-issues-and-pull-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md b/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md index 8a73915e10..665fac7c64 100644 --- a/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md +++ b/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md @@ -60,7 +60,7 @@ For pull requests, you can also use search to: {% note %} -**Note:** {% data reusables.pull_requests.large-search-workaround %} You can do this by adding the `org:`, `user:`, or `repo:` qualifier to your search. +**Note:** {% data reusables.pull_requests.large-search-workaround %} You can limit your search with the `org:`, `user:`, or `repo:` qualifiers. {% endnote %} From f647e2e869d6eaa171c37117c517fc6e5e42bd30 Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Tue, 24 Aug 2021 12:53:08 +0200 Subject: [PATCH 6/8] Update using-search-to-filter-issues-and-pull-requests.md --- .../using-search-to-filter-issues-and-pull-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md b/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md index 665fac7c64..e18682d0de 100644 --- a/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md +++ b/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md @@ -60,7 +60,7 @@ For pull requests, you can also use search to: {% note %} -**Note:** {% data reusables.pull_requests.large-search-workaround %} You can limit your search with the `org:`, `user:`, or `repo:` qualifiers. +**Note:** {% data reusables.pull_requests.large-search-workaround %} You can limit your search with the `org:`, `user:`, or `repo:` qualifiers. For more information, see "[Searching issues and pull requests](/articles/searching-issues)" {% endnote %} From 03dc1395a52bd30b47c8bff7dbab84176bb9735a Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Tue, 24 Aug 2021 12:55:34 +0200 Subject: [PATCH 7/8] Update searching-issues-and-pull-requests.md --- .../searching-issues-and-pull-requests.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md b/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md index 9b3c7f569d..77f2e8acd6 100644 --- a/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md @@ -50,17 +50,16 @@ With the `in` qualifier you can restrict your search to the title, body, comment To search issues and pull requests in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search issues and pull requests in a specific repository, you can use the `repo` qualifier. +{% data reusables.pull_requests.large-search-workaround %} + + | Qualifier | Example | ------------- | ------------- | user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) matches issues with the word "ubuntu" from repositories owned by @defunkt. | org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) matches issues in repositories owned by the GitHub organization. | repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) matches issues from @mozilla's shumway project that were created before March 2012. -{% note %} -**Note:** {% data reusables.pull_requests.large-search-workaround %} - -{% endnote %} ## Search by open or closed state From 1e469541ec212cc9ebdcbe2a402436c32b5e7abe Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Tue, 24 Aug 2021 13:15:07 +0200 Subject: [PATCH 8/8] Update content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md Co-authored-by: Matt Pollard --- .../using-search-to-filter-issues-and-pull-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md b/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md index e18682d0de..adcb54b0cc 100644 --- a/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md +++ b/content/github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md @@ -60,7 +60,7 @@ For pull requests, you can also use search to: {% note %} -**Note:** {% data reusables.pull_requests.large-search-workaround %} You can limit your search with the `org:`, `user:`, or `repo:` qualifiers. For more information, see "[Searching issues and pull requests](/articles/searching-issues)" +**Note:** {% data reusables.pull_requests.large-search-workaround %} You can limit your search with the `org:`, `user:`, or `repo:` qualifiers. For more information, see "[Searching issues and pull requests](/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-within-a-users-or-organizations-repositories)." {% endnote %}