Skip to content

Commit 4baf121

Browse files
authored
Make public projects boards and gists internal for AE (#17247)
1 parent 0f30a80 commit 4baf121

18 files changed

Lines changed: 43 additions & 43 deletions
3.37 KB
Loading
23.9 KB
Loading
21.2 KB
Loading
17.3 KB
Loading
15.2 KB
Loading
Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Changing project board visibility
3-
intro: 'As an organization owner or project board admin, you can make a project board public or private.'
3+
intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.'
44
redirect_from:
55
- /articles/changing-project-board-visibility
66
versions:
@@ -13,12 +13,12 @@ versions:
1313

1414
{% tip %}
1515

16-
**Tip:** When you make your project board public, 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)."
16+
**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}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)."
1717

1818
{% endtip %}
1919

20-
1. Navigate to the project board you want to make public or private.
20+
1. Navigate to the project board you want to make {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.
2121
{% data reusables.project-management.click-menu %}
2222
{% data reusables.project-management.access-collaboration-settings %}
23-
4. Under "Visibility", select **Public** or **Private**. Then, click **Save**.
24-
![Public and private radio buttons](/assets/images/help/projects/project-board-visibility-options.png)
23+
{% data reusables.project-management.choose-visibility %}
24+
1. Click **Save**.

content/github/managing-your-work-on-github/copying-a-project-board.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,6 @@ A project board's automation is also enabled by default. For more information, s
2727
![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png)
2828
7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)."
2929
![Select automation settings for copied project board](/assets/images/help/projects/copied-project-board-automation-settings.png)
30-
8. If you are copying an organization-owned project board, under "Visibility", select whether you want your copied project board to be private or public.
31-
![Select visibility settings for copied project board](/assets/images/help/projects/copied-project-board-visibility-settings.png)
30+
{% data reusables.project-management.choose-visibility %}
3231
9. Click **Copy project**.
3332
![Confirm Copy button](/assets/images/help/projects/confirm-copy-project-board.png)

content/github/managing-your-work-on-github/creating-a-project-board.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,7 @@ You can also configure workflow automations to keep your project board in sync w
3030
{% data reusables.project-management.click-new-project %}
3131
{% data reusables.project-management.create-project-name-description %}
3232
{% data reusables.project-management.choose-template %}
33+
{% data reusables.project-management.choose-visibility %}
3334
{% data reusables.project-management.linked-repositories %}
3435
{% data reusables.project-management.create-project-button %}
3536
{% data reusables.project-management.add-column-new-project %}
@@ -49,6 +50,7 @@ You can also configure workflow automations to keep your project board in sync w
4950
{% data reusables.project-management.click-new-project %}
5051
{% data reusables.project-management.create-project-name-description %}
5152
{% data reusables.project-management.choose-template %}
53+
{% data reusables.project-management.choose-visibility %}
5254
{% data reusables.project-management.linked-repositories %}
5355
{% data reusables.project-management.create-project-button %}
5456
{% data reusables.project-management.add-column-new-project %}

content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ For example, if an organization owner has given all organization members read pe
3030

3131
### Project board visibility
3232

33-
{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to public and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)."
33+
{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)."
3434

3535
### Further reading
3636

content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ There are three levels of permissions for project board collaborators:
2222
The project board owner and collaborators with admin access have full control of the project board. In addition to all the permissions allowed by project board collaborators, a project board owner and collaborator with admin access can:
2323

2424
- [Manage, view, and add collaborators](/articles/managing-access-to-your-user-account-s-project-boards)
25-
- [Configure a project board as public or private](/articles/changing-project-board-visibility)
25+
- [Configure a project board as {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private](/articles/changing-project-board-visibility)
2626
- [Delete a project board](/articles/deleting-a-project-board/)
2727
- [Close a project board](/articles/closing-a-project-board/)
2828
- [Reopen a closed project board](/articles/reopening-a-closed-project-board)
@@ -51,7 +51,7 @@ Collaborators with write access to a user-owned project board can:
5151

5252
### Project board visibility
5353

54-
You can change the project board's visibility from private to public and back again. By default, user-owned project boards are private. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)."
54+
You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. By default, user-owned project boards are private. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)."
5555

5656
### Further reading
5757

0 commit comments

Comments
 (0)