You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: website/docs/r/repository_collaborators.html.markdown
+15-10
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,10 @@ github_team_repository or they will fight over what your policy should be.
14
14
15
15
This resource allows you to manage all collaborators for repositories in your
16
16
organization or personal account. For organization repositories, collaborators can
17
-
have explicit (and differing levels of) read, write, or administrator access to
18
-
specific repositories, without giving the user full organization membership.
17
+
have explicit (and differing levels of) read, write, or administrator access to
18
+
specific repositories, without giving the user full organization membership.
19
19
For personal repositories, collaborators can only be granted write
20
-
(implicitly includes read) permission.
20
+
(implicitly includes read) permission.
21
21
22
22
When applied, an invitation will be sent to the user to become a collaborators
23
23
on a repository. When destroyed, either the invitation will be cancelled or the
@@ -31,7 +31,7 @@ Further documentation on GitHub collaborators:
31
31
-[Adding outside collaborators to your personal repositories](https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories)
32
32
-[Adding outside collaborators to repositories in your organization](https://help.github.com/articles/adding-outside-collaborators-to-repositories-in-your-organization/)
33
33
-[Converting an organization member to an outside collaborators](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)
*`user` - (Optional) List of users to grant access to the repository.
69
+
*`team` - (Optional) List of teams to grant access to the repository.
70
+
*`ignore_team` - (Optional) List of teams to ignore when checking for repository access. This supports ignoring teams granted access at an organizational level.
70
71
71
72
The `user` block supports:
72
73
@@ -77,16 +78,20 @@ The `user` block supports:
77
78
78
79
The `team` block supports:
79
80
80
-
*`team_id` - (Required) The GitHub team id or the GitHub team slug
81
+
*`team_id` - (Required) The GitHub team id or the GitHub team slug.
81
82
*`permission` - (Optional) The permission of the outside collaborators for the repository.
82
83
Must be one of `pull`, `triage`, `push`, `maintain`, `admin` or the name of an existing [custom repository role](https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization) within the organisation. Defaults to `pull`.
83
84
Must be `push` for personal repositories. Defaults to `push`.
84
85
86
+
The `team_ignore` block supports:
87
+
88
+
*`team_id` - (Required) The GitHub team id or the GitHub team slug.
89
+
85
90
## Attribute Reference
86
91
87
92
In addition to the above arguments, the following attributes are exported:
88
93
89
-
*`invitation_ids` - Map of usernames to invitation ID for any users added as part of creation of this resource to
94
+
*`invitation_ids` - Map of usernames to invitation ID for any users added as part of creation of this resource to
90
95
be used in [`github_user_invitation_accepter`](./user_invitation_accepter.html).
0 commit comments