Missing author_association field in list_issues and pull request responses
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start by reading pkg/github/issues.go and pkg/github/minimal_types.go, focusing on IssueFragment, fragmentToMinimalIssue(), MinimalPullRequest, and convertToMinimalPullRequest(). Verify the list_issues GraphQL response and the list_pull_requests and pull_request_read REST responses; the work is done when each includes author_association with the available author association value.
Written by the indexing model from the issue text.
Description
Summary
The author_association field is missing from several MCP response types, which prevents downstream consumers from determining author permissions (e.g., OWNER, MEMBER, COLLABORATOR, CONTRIBUTOR, NONE).
Affected Endpoints
1. list_issues (GraphQL path)
IssueFragmentstruct does not requestauthorAssociationin the GraphQL queryfragmentToMinimalIssue()does not populateAuthorAssociationinMinimalIssue- Note: The REST path in
convertToMinimalIssue()correctly setsAuthorAssociation: issue.GetAuthorAssociation()
2. list_pull_requests and pull_request_read (REST path)
MinimalPullRequeststruct is missing theauthor_associationfield entirelyconvertToMinimalPullRequest()does not set it- The raw
*github.PullRequestfrom the go-github library hasAuthorAssociationavailable viapr.GetAuthorAssociation()
Already Working
issue_read(single issue GET) — uses RESTconvertToMinimalIssue()which includesauthor_association✅get_review_comments—MinimalPullRequestReviewincludesauthor_association✅
Impact
Consumers that rely on author_association to determine author trust level (OWNER, MEMBER, COLLABORATOR, CONTRIBUTOR, NONE) cannot make correct decisions when this field is missing from list_issues and pull request responses.
For example, a repo admin's issues are incorrectly treated as untrusted because their author_association of "MEMBER" is not present in the response.
Suggested Fix
For list_issues (GraphQL):
- Add
AuthorAssociation githubv4.StringtoIssueFragmentstruct inissues.go - Set
AuthorAssociation: string(fragment.AuthorAssociation)infragmentToMinimalIssue()inminimal_types.go
For pull requests (REST):
- Add
AuthorAssociation string \x60json:"author_association,omitempty"\x60toMinimalPullRequeststruct inminimal_types.go - Set
AuthorAssociation: pr.GetAuthorAssociation()inconvertToMinimalPullRequest()inminimal_types.go
References
pkg/github/issues.go—IssueFragmentstructpkg/github/minimal_types.go—MinimalIssue,MinimalPullRequest,fragmentToMinimalIssue(),convertToMinimalPullRequest()
- Dominant language
- Go
- Stars
- 33.1k
- Forks
- 5k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 25
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/github-mcp-server
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/github-mcp-server#3235 ·
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
github/github-mcp-server#3042 · 2 comments ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/github-mcp-server#3032 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
github/github-mcp-server#2803 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/github-mcp-server#2740 ·
All issues in github/github-mcp-server
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NVIDIA/gpu-operator#2955 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
cisagov/vulnrichment#337 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100