`@agent` on a Forgejo issue comment does nothing, no log, no message

Open
#197 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
backend

Research direction

Compare how the backend handles an @agent mention in a pull request comment with how it handles one in an issue comment, starting from the comment-event entry point that receives Forgejo webhooks. Find where the issue-comment path drops the trigger without logging. Done when an @agent issue comment starts a run, or when it logs the reason it was skipped.

Written by the indexing model from the issue text.

Description

@agent in a pull request comment works. The same text in an issue comment does nothing at all.
No run starts, nothing is logged, and the user gets no hint why.

Dominant language
Go
Stars
421
Forks
50
Avg merge
17h 34m
Merged PRs (30d)
80

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Windshiftapp/core

All issues in Windshiftapp/core

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.