access: go-assignees and go-editors

[qiulaidongfeng]

See https://go.dev/wiki/GithubAccess

I have come across issues that can be closed many time, for example #7876 , #50617, #28262 , #52767
I wish I could close this issue myself to make better use of the time I and others have spent contributing to go.
For example #7876 , if I can close that issue so that no one else has to deal with closing the issue on their own time.

For example, #63768, if I have permission, I can modify the title and other operations by myself, so that others do not have to deal with these things in their own time.

For example, #54709, that issue is not difficult to fix the correct behavior, the difficulty is not to affect the performance, if I can't fix it on https://go.dev/cl/554456, I can add a help wanted label, so that people who are interested in trying can find it more easily.

Github: @qiulaidongfeng

Thanks in advance!

cc @golang/release

[qiulaidongfeng]

Friendly ping @golang/release.

I now have come across another issue(#64549) that I can turn off. https://go-review.googlesource.com/c/go/+/568339 fixed it.

I wish I could close this issue myself to make better use of the time I and others have spent contributing to go.

[dmitshur]

Hi @qiulaidongfeng, thanks for your interest and contributions to Go.

We considered this request. Similarly to #66611 (comment), when considering granting "go-editors" GitHub access, we look for history of interactions on the issue tracker that demonstrates careful thought, consideration of trade-offs, and good understanding of project conventions and priorities. We're going to decline this request at this time. Thanks again.

I have sent you an invite to the "go-assignees" group (https://go.dev/wiki/GithubAccess#assignees).