fix(forgejo): handle issue-body mentions and all bot aliases #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/issue-body-mentions-and-aliases"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue #4820 was filed with
@codetether handle this issuein the body and the bot never responded.Three defects:
issues/opened, but_contextreturnedNonefor anything exceptissue_comment. Now handled.@codetether-botmatched the shortercodetetherslug, leaving-botin the text intent parsing saw. Mentions are now matched on word boundaries, and@codetether,@codetether-bot, and@codetether-agentare all recognized (extendable viaCODETETHER_BOT_ALIASES).@codetetheringandcodetether@example.comcorrectly do not match.session_idwas silently discarded.TaskReleaseRequestdid not declare the field workers send, so Pydantic dropped it and no task ever recorded a session — which is why the Forgejo "Session transcript" panel could never resolve a transcript. It is now declared and persisted.The self-authored guard covers every alias, but only inspects the author of the current event: the bot owns some repositories, so a human comment on a bot-opened issue is still real input.
Also enabled the
issuesevent on system hook 8 and repo hook 2 (verifiedissues_on = true).Validation: 84 tests pass.