| --- |
| title: GitHubAccess |
| --- |
| |
| There are two types of GitHub access described here, with different powers & responsibilities. Only ask for access if you're an active member of the community. New contributors should participate in the GitHub & Gerrit review process for some time before requesting access. |
| |
| (For Gerrit access, see [GerritAccess](/wiki/GerritAccess)) |
| |
| ## Assignees |
| |
| The "go-assignees" group is a read-only group granting no special access, other than it allows the users in the group to be assigned issues. |
| |
| In general, Go doesn't use the "Assigned to" field of bugs much. Instead, we just leave a comment saying we'll work on it. But if you want this access, reference https://github.com/orgs/golang/teams/go-assignees and your GitHub username in your issue requesting access. |
| |
| ## Editors |
| |
| The "go-editors" group is the set of people who can edit metadata on issues. |
| |
| To request this type of access, reference https://github.com/orgs/golang/teams/go-editors and your GitHub username in your issue requesting access. |
| |
| Please do not edit any field you're not confident about. Feel free to ask for second opinions. |
| |
| ## Requesting Access |
| |
| To request any of the access types above, file a new issue (https://go.dev/issue/new?title=access:+&body=See+https://go.dev/wiki/GitHubAccess.) and state which access you want (its name and group URL). |
| |
| ## Once you have access |
| |
| Go help garden! See [Gardening](/wiki/Gardening). |
| |
