Repository navigation
[backport] get_parent method for issue_read (upstream main) #15
Description
Summary
Adds a get_parent method to the issue_read consolidated tool — the upward counterpart to the existing get_sub_issues. Uses the GraphQL Issue.parent field and returns {"parent": null} when the issue is not a sub-issue. Kept always-on (not feature-gated) to mirror get_sub_issues.
Changes: pkg/github/issues.go +53/-3 lines; pkg/github/issues_test.go +122 lines.
Upstream reference
- version: upstream main (post v1.4.0, unreleased)
- commits: github@9430064
- PR: Add get_parent method to issue_read github/github-mcp-server#2726
Fork conflict
Design note. The fork's issue_graph tool traverses sub-issues downward (BFS). get_parent is the upward complement. Both are useful for autonomous agents navigating issue hierarchies. get_parent is in issues.go (not the fork's custom files) and is purely additive — no conflict.
Context
An agent using issue_graph to traverse sub-issues downward had no efficient way to navigate upward to find an issue's parent epic. get_parent closes this gap, completing the vertical traversal API.
Activity
gastrodon commentedon Jun 27, 2026
Unified Changelog — upstream main since v1.4.0
See #10 for the full changelog. Summary:
get_parentforissue_readissue_writeshow_ui, centralize show/deferdelete:trueon issue fieldsui_getpaginationissue_writeform gatingadd_comment_to_pending_reviewgastrodon commentedon Jun 27, 2026
No-op. The fork already has
get_parentinpkg/github/issues.go(line 620+). The method uses the GraphQLIssue.parentfield and returns{"parent": null}for top-level issues. Tests are present inissues_test.go.