mirror of
https://github.com/golang/go.git
synced 2025-05-05 15:43:04 +00:00
Created GithubAccess (markdown)
parent
a83b0429b2
commit
12e9c5e46e
21
GithubAccess.md
Normal file
21
GithubAccess.md
Normal file
@ -0,0 +1,21 @@
|
||||
# Github Access
|
||||
|
||||
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. See https://golang.org/wiki/Gardening.
|
||||
|
||||
## Assignees
|
||||
|
||||
The "go-assignees" group is a read-only group granting no special access, other than it allows the users inthe 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 email requesting access.
|
||||
|
||||
## Editors
|
||||
|
||||
The poorly named "go-approvers" 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-approvers and your Github username in your email requesting access.
|
||||
|
||||
Please do not edit any field you're not confident about. Feel free to ask for second opinions.
|
||||
|
||||
## Requesting Access
|
||||
|
||||
To request either of the access types above, email bradfitz (at golang) and state which access you want (its URL), and state your Github username.
|
Loading…
x
Reference in New Issue
Block a user