Accept blocked_owner/blocked_repo and blocking_owner/blocking_repo (default to the path issue repo) and send them in the IssueMeta body so Gitea can resolve cross-repository links.
Clarify blocked-by vs blocks in the tool descriptions, and that these endpoints 404 when the repo has issue dependencies disabled.
Follow-up to the issue dependency/blocker tools.
- Accept `blocked_owner`/`blocked_repo` and `blocking_owner`/`blocking_repo` (default to the path issue repo) and send them in the IssueMeta body so Gitea can resolve cross-repository links.
- Add `issue_read` method `check_blocked` summarizing open blockers (`blocked`, `total_dependencies`, `open_blockers`, `blockers`, `open`).
- Clarify blocked-by vs blocks in the tool descriptions, and that these endpoints 404 when the repo has issue dependencies disabled.
Send blocked_owner/blocked_repo and blocking_owner/blocking_repo in the
IssueMeta body so Gitea can resolve cross-repository links. Default those
fields to the path issue's owner/repo.
Add issue_read method check_blocked to summarize open blockers, and
document that dependency endpoints 404 when the repo has issue
dependencies disabled.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to the issue dependency/blocker tools.
blocked_owner/blocked_repoandblocking_owner/blocking_repo(default to the path issue repo) and send them in the IssueMeta body so Gitea can resolve cross-repository links.issue_readmethodcheck_blockedsummarizing open blockers (blocked,total_dependencies,open_blockers,blockers,open).