Merge branch 'main' into jules-5659

Author: jules-p

.devcontainer/devcontainer.json

@@ -21,14 +21,18 @@
 		"davidanson.vscode-markdownlint",
 		"bierner.markdown-preview-github-styles",
 		"yzhang.markdown-all-in-one",
-		"streetsidesoftware.code-spell-checker"
+		"streetsidesoftware.code-spell-checker",
+		"hubwriter.open-reusable"
 	],
 
 	// Use 'forwardPorts' to make a list of ports inside the container available locally.
 	"forwardPorts": [4000],
 
 	// Use 'postCreateCommand' to run commands after the container is created.
 	 "postCreateCommand": "npm ci && npm run build",
+		 
+	// Use 'postCreateCommand' to install the Open Reusables extension.
+	 "postCreateCommand": "code --install-extension .vscode/open-reusable-1.3.0.vsix",
 
 	// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
 	"remoteUser": "node"

.vscode/open-reusable-1.3.0.vsix

@@ -2,4 +2,6 @@
   "files.exclude": {
     "**/translations": true
   }
-}
+  "workbench.editor.enablePreview": false,
+  "workbench.editor.enablePreviewFromQuickOpen": false  
+}

.vscode/settings.json

@@ -19,55 +19,55 @@ Use the project command palette to quickly change settings and run commands in y
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing any part of a command or navigate through the command palette window to find a command. See the next sections for more examples of commands.
 
-## Change layout
+## Changing the project layout
 
 You can view your project as a table or as a board.
 
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing "Switch layout".
-3. Select the desired command (for example: "Switch layout: Table").
-3. Alternatively, select the drop-down menu next to a view name and click **Table** or **Board**.
+3. Choose the required command. For example, **Switch layout: Table**.
+3. Alternatively, click the drop-down menu next to a view name and click **Table** or **Board**.
 
-## Show or hide fields
+## Showing and hiding fields
 
 You can show or hide a specific field.
 
 In table layout:
 
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing the action you want to take ("show" or "hide") or the name of the field.
-3. Select the desired command (for example: "Show: Milestone").
+3. Choose the required command. For example, **Show: Milestone**.
 4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} to the right of the table. In the drop-down menu that appears, indicate which fields to show or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
-5. Alternatively, select the drop-down menu next to the field name and click **Hide field**.
+5. Alternatively, click the drop-down menu next to the field name and click **Hide field**.
 
 In board layout:
 
-1. Select the drop-down menu next to the view name.
+1. Click the drop-down menu next to the view name.
 2. Under **configuration**, click {% octicon "list-unordered" aria-label="the unordered list icon" %}.
-3. In the menu that appears, select fields to add them and deselect fields to remove them from the view.
+3. In the menu that's displayed, select fields to add them and deselect fields to remove them from the view.
 
-## Reorder fields
+## Reordering fields
 
 You can change the order of fields.
 
 1. Click the field header.
-2. While clicking, drag the field to the desired location.
+2. While clicking, drag the field to the required location.
 
-## Reorder rows
+## Reordering rows
 
 In table layout, you can change the order of rows.
 
 1. Click the number at the start of the row.
-2. While clicking, drag the row to the desired location.
+2. While clicking, drag the row to the required location.
 
-## Sort
+## Sorting by field values
 
 In table layout, you can sort items by a field value.
 
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing "Sort by" or the name of the field you want to sort by.
-3. Select the desired command (for example: "Sort by: Assignees, asc").
-4. Alternatively, select the drop-down menu next to the field name that you want to sort by and click **Sort ascending** or **Sort descending**.
+3. Choose the required command. For example, **Sort by: Assignees, asc**.
+4. Alternatively, click the drop-down menu next to the field name that you want to sort by and click **Sort ascending** or **Sort descending**.
 
 {% note %}
 
@@ -79,12 +79,12 @@ Follow similar steps to remove a sort.
 
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing "Remove sort-by".
-3. Select the "Remove sort-by" command.
-4. Alternatively, select the drop-down menu next to the view name and click the menu item that indicates the current sort.
+3. Choose **Remove sort-by**.
+4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current sort.
 
-## Group
+## Grouping by field values
 
-In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by `Status` and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`.
+In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`.
 
 {% note %}
 
@@ -94,17 +94,17 @@ In the table layout, you can group items by a custom field value. When items are
 
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing "Group by" or the name of the field you want to group by.
-3. Select the desired command (e.g. "Group by: Status").
-4. Alternatively, select the drop-down menu next to the field name that you want to group by and click **Group by values**.
+3. Choose the required command. For example, **Group by: Status**.
+4. Alternatively, click the drop-down menu next to the field name that you want to group by and click **Group by values**.
 
 Follow similar steps to remove a grouping.
 
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing "Remove group-by".
-3. Select the "Remove group-by" command.
-4. Alternatively, select the drop-down menu next to the view name and click the menu item that indicates the current grouping.
+3. Choose **Remove group-by**.
+4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current grouping.
 
-## Filter
+## Filtering rows
 
 Click {% octicon "search" aria-label="the search icon" %} at the top of the table to show the "Filter by keyword or field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear.
 
@@ -118,41 +118,66 @@ Alternatively, use the command palette.
 
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing "Filter by" or the name of the field you want to filter by.
-3. Select the desired command (e.g. "Filter by Status").
-4. Enter the value that you want to filter for (for example: "In progress"). You can also filter for the absence of specific values (for example: "Exclude status") or the absence of all values (for example: "No status").
+3. Choose the required command. For example, **Filter by Status**.
+4. Enter the value that you want to filter for. For example: "In progress". You can also filter for the absence of specific values (for example, choose "Exclude status" then choose a status) or the absence of all values (for example, "No status").
 
 In board layout, you can click on item data to filter for items with that value. For example, click on an assignee to show only items for that assignee. To remove the filter, click the item data again.
 
-## Save views
+## Creating a project view
 
-Saved views allow you to quickly view specific aspects of your project. For example, you could have the following:
-- a view that shows all un-started items (filter on "Status").
-- a view that shows the workload for each team member (group by "Asssignee" and filter on "Status").
-- a view that shows the items with the earliest target ship date (sort by a date field).
+Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project. 
 
-The following steps demonstrate how to add a new view:
+For example, you can have:
+- A view that shows all items not yet started (filter on "Status").
+- A view that shows the workload for each team member (group by "Assignee" and filter on "Status").
+- A view that shows the items with the earliest target ship date (sort by a date field).
+
+To add a new view:
 
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing "New view" (to create a new view) or "Duplicate view" (to duplicate the current view).
-3. Select the desired command.
+3. Choose the required command.
 4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view.
-5. Alternatively, select the drop-down menu next to a view name and click **Duplicate view**.
+5. Alternatively, click the drop-down menu next to a view name and click **Duplicate view**.
+
+The new view is automatically saved.
+
+## Saving changes to a view
 
-When you make changes to a view, a dot appears next to the view name to indicate that the view has been modified. If you don't want to save the changes, you can ignore this indicator. To save the view for all project members:
+When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes. 
 
+![Unsaved changes indicator](/assets/images/help/projects/unsaved-changes.png)
+
+If you don't want to save the changes, you can ignore this indicator. No one else will see your changes.
+
+To save the current configuration of the view for all project members:
 1. {% data reusables.projects.open-command-palette %}
 1. Start typing "Save view" or "Save changes to new view".
-1. Select the desired command.
-1. Alternatively, select the drop-down menu next to a view name and click **Save view** or **Save changes to new view**.
+1. Choose the required command.
+1. Alternatively, click the drop-down menu next to a view name and click **Save view** or **Save changes to new view**.
 
-To rename a view, double click on the view name and type the desired name.
+## Reordering saved views
 
-To delete a view:
+To change the order of the tabs that contain your saved views, click and drag a tab to a new location.
 
+The new tab order is automatically saved.
+
+## Renaming a saved view
+
+To rename a view:
+1. Double click the name in the project tab.
+1. Change the name.
+1. Press Enter, or click outside of the tab.
+
+The name change is automatically saved.
+
+## Deleting a saved view
+
+To delete a view:
 1. {% data reusables.projects.open-command-palette %}
 2. Start typing "Delete view".
-3. Select the desired command.
-4. Alternatively, select the drop-down menu next to a view name and click **Delete view**.
+3. Choose the required command.
+4. Alternatively, click the drop-down menu next to a view name and click **Delete view**.
 
 ## Further reading
 

assets/images/help/projects/unsaved-changes.png

@@ -15,9 +15,9 @@ topics:
 
 ## About project access
 
-Admins of organization-level projects can manage access to their organization's projects for everyone in the organization. Organization project admins can also manage access for individual organization members.
+Admins of organization-level projects can manage access for the entire organization, for teams, and for individual organization members.
 
-Admins of user-level projects can invite collaborators and manage access for individual collaborators.
+Admins of user-level projects can invite individual collaborators and manage their access.
 
 Project admins can also control the visibility of their project for everyone on the internet. For more information, see "[Managing the visibility of your projects](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)."
 
@@ -35,24 +35,29 @@ The default base role is `write`, meaning that everyone in the organization can
    - **Write**: Everyone in the organization can see and edit the project. Organization owners are also admins for the project.
    - **Admin**: Everyone in the organization is an admin for the project.
 
-### Managing access for individual members of your organization
+### Managing access for teams and individual members of your organization
 
-You can also add individual organization members as collaborators to your project. Only organization members can be added as collaborators to organization projects.
+You can also add teams, and individual organization members, as collaborators. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+
+You can only invite an individual user to collaborate on your organization-level project if they are a member of the organization.
 
 {% data reusables.projects.project-settings %}
 1. Click **Manage access**.
-1. Under **Invite collaborators**, search for the organization member that you want to invite.
+1. Under **Invite collaborators**, search for the team or organization member that you want to invite.
 1. Select the role for the collaborator.
-   - **Read**: The individual can view the project.
-   - **Write**: The individual can view and edit the project.
-   - **Admin**: The individual can view, edit, and add new collaborators to the project.
+   - **Read**: The team or individual can view the project.
+   - **Write**: The team or individual can view and edit the project.
+   - **Admin**: The team or individual can view, edit, and add new collaborators to the project.
 1. Click **Invite**.
 
 ### Managing access of an existing collaborator on your project
 
 {% data reusables.projects.project-settings %}
 1. Click **Manage access**.
 1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
+
+   You can use the **Type** and **Role** drop-down menus to filter the access list.
+
 1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s).
 
 ## Managing access for user-level projects
@@ -79,4 +84,7 @@ This only affects collaborators for your project, not for repositories in your p
 {% data reusables.projects.project-settings %}
 1. Click **Manage access**.
 1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
+
+   You can use the **Role** drop-down menu to filter the access list.
+
 1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s).