Frontmatter
| title | Adds Blocked By and Blocking to issue relationship tool |
| author | MannXo |
| state | Merged |
| createdAt | Nov 12, 2025, 11:21 AM |
| updatedAt | Nov 12, 2025, 3:23 PM |
| closedAt | Nov 12, 2025, 3:23 PM |
| mergedAt | Nov 12, 2025, 3:23 PM |
| branches | dev ← enhancement/blocked-by-blocking-relationships |
| url | https://github.com/neomjs/neo/pull/7753 |
Merged

tobiu
commented on Nov 12, 2025, 3:22 PM
Input from Gemini 2.5 pro:
✦ The core functionality of adding "blocked by" and "blocking" relationships is a valuable enhancement. I'm approving this PR.
However, during the review, the following areas for improvement were identified and will be addressed in separate follow-up tickets to avoid merge conflicts and keep this PR focused:
- Issue #7757: Optimize GraphQL responses for
ADD_BLOCKED_BYandREMOVE_BLOCKED_BYmutations. The current responses fetch more data than necessary.- Issue #7758: Extract inline GraphQL queries from
IssueService.mjsto thequeriesfolder for better separation of concerns.- Issue #7759: Move "blocked by" and "blocking" relationship information from the issue body to the frontmatter in
IssueSyncer.mjsfor improved data structure and consistency.Thanks for the contribution!
summary:
Extends the existing
update_issue_relationshiptool to support GitHub's "blocked by" and "blocking" relationship types, enabling dependency tracking between issues.Closes #7749
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills this requirement:
devbranch, not themainbranchIf adding a new feature, the PR's description includes:
Other information: