feat: maintain and triage user permissions in orgs (#62)

Co-authored-by: Octokit Bot <33075676+octokitbot@users.noreply.github.com>

Author: github-actions[bot]

docs/repos/getCollaboratorPermissionLevel.md

@@ -1,6 +1,6 @@
 # Review a user's permission level
 
-Possible values for the `permission` key: `admin`, `write`, `read`, `none`.
+Checks the repository permission of a collaborator. The possible repository permissions are `admin`, `write`, `read`, and `none`.
 
 ```js
 octokit.repos.getCollaboratorPermissionLevel({

docs/repos/updateInvitation.md

@@ -36,7 +36,7 @@ invitation_id parameter
 </td></tr>
 <tr><td>permissions</td><td>no</td><td>
 
-The permissions that the associated user will have on the repository. Valid values are `read`, `write`, and `admin`.
+The permissions that the associated user will have on the repository. Valid values are `read`, `write`, `maintain`, `triage`, and `admin`.
 
 </td></tr>
   </tbody>

docs/teams/addOrUpdateRepoInOrg.md

@@ -4,6 +4,8 @@ To add a repository to a team or update the team's permission on a repository, t
 
 **Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/:org_id/team/:team_id/repos/:owner/:repo`.
 
+For more information about the permission levels, see "[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)" in the GitHub Help documentation.
+
 ```js
 octokit.teams.addOrUpdateRepoInOrg({
   org,
@@ -49,7 +51,9 @@ repo parameter
 The permission to grant the team on this repository. Can be one of:  
 \* `pull` - team members can pull, but not push to or administer this repository.  
 \* `push` - team members can pull and push, but not administer this repository.  
-\* `admin` - team members can pull, push and administer this repository.
+\* `admin` - team members can pull, push and administer this repository.  
+\* `maintain` - team members can manage the repository without access to sensitive or destructive actions. Recommended for project managers. Only applies to repositories owned by organizations.  
+\* `triage` - team members can proactively manage issues and pull requests without write access. Recommended for contributors who triage a repository. Only applies to repositories owned by organizations.
 
 If no permission is specified, the team's `permission` attribute will be used to determine what permission to grant the team on this repository.
 

docs/teams/checkManagesRepoInOrg.md

@@ -1,6 +1,6 @@
 # Check if a team manages a repository
 
-Checks whether a team has `admin`, `push`, or `pull` permission for a repository. Repositories inherited through a parent team will also be checked.
+Checks whether a team has `admin`, `push`, `maintain`, `triage`, or `pull` permission for a repository. Repositories inherited through a parent team will also be checked.
 
 **Note:** You can also specify a team by `org_id` and `team_id` using the route `GET /organizations/:org_id/team/:team_id/repos/:owner/:repo`.