tools.gitea_integration module
Gitea shortcuts for smk/stargazer-v3 on git.neko.li (delegates to shared credentials).
- async tools.gitea_integration.gitea_open_issue(title, body, ctx=None)[source]
Open a new issue on the canonical
smk/stargazer-v3Gitea repo.Convenience shortcut that hardcodes the owner/repo (
DEFAULT_OWNER/DEFAULT_REPO) so callers need only supply the issuetitleandbody. It lazily imports and delegates totools.gitea_tools.gitea_create_issue, which performs the authenticated HTTPPOSTagainst the Gitea API ongit.neko.liusing the shared repo credentials; all network access and error handling live in that shared helper. Thectxis forwarded so the underlying tool can resolve credentials and platform state.This coroutine is registered as the
gitea_open_issuehandler in this module’sTOOLSlist (and appears inclassifiers/tool_prefix_groups.pyfor routing), so it is invoked via the tool-dispatch layer rather than by direct internal calls; no direct by-name callers were found.- Parameters:
title (
str) – The issue title.body (
str) – The issue body in Markdown.ctx (
ToolContext|None) – Tool execution context forwarded to the shared Gitea helper for credential/platform resolution.
- Return type:
- Returns:
The string result produced by
gitea_create_issue(typically a success/summary message or serialized issue details).
- async tools.gitea_integration.gitea_comment_issue(issue_id, body, ctx=None)[source]
Post a comment on an existing issue in
smk/stargazer-v3.Convenience shortcut that pins the owner/repo (
DEFAULT_OWNER/DEFAULT_REPO) and lazily delegates totools.gitea_tools.gitea_create_issue_comment, which issues the authenticated HTTPPOSTto the Gitea API ongit.neko.liusing the shared repo credentials. All network I/O and error handling are owned by that shared helper;ctxis forwarded for credential/platform resolution.Registered as the
gitea_comment_issuehandler in this module’sTOOLSlist (and listed inclassifiers/tool_prefix_groups.pyfor routing), so it is reached through the tool-dispatch layer; no direct by-name internal callers were found.- Parameters:
issue_id (
int) – The numeric id (issue number) of the target issue.body (
str) – The comment text in Markdown.ctx (
ToolContext|None) – Tool execution context forwarded to the shared Gitea helper.
- Return type:
- Returns:
The string result produced by
gitea_create_issue_comment(typically a success/summary message or serialized comment details).
- async tools.gitea_integration.gitea_close_issue(issue_id, ctx=None)[source]
Close an existing issue in
smk/stargazer-v3.Convenience shortcut that pins the owner/repo (
DEFAULT_OWNER/DEFAULT_REPO) and lazily delegates totools.gitea_tools.gitea_update_issuewithstate="closed". That shared helper performs the authenticated HTTPPATCHagainst the Gitea API ongit.neko.liusing the shared repo credentials and owns all network I/O and error handling;ctxis forwarded for credential/platform resolution.Registered as the
gitea_close_issuehandler in this module’sTOOLSlist (and listed inclassifiers/tool_prefix_groups.pyfor routing), so it is invoked through the tool-dispatch layer; no direct by-name internal callers were found.- Parameters:
issue_id (
int) – The numeric id (issue number) of the issue to close.ctx (
ToolContext|None) – Tool execution context forwarded to the shared Gitea helper.
- Return type:
- Returns:
The string result produced by
gitea_update_issue(typically a success/summary message or serialized issue details).