Forgejo: trigger on comments on agent-opened issues/PRs #84
No reviewers
Labels
No labels
Agent
Ignore
Agent
In Progress
Agent
Planned
Agent
Planning
Agent
Ready
Agent
Triage
Compat
Breaking
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
lucas/omp-deck!84
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/issue-82-agent-artifact-trigger"
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?
Implements the plan in #82.
detectAddressedtakes a requiredopening(the description as entry id 0). The quoted-reply and follows-agent rules now run over[opening, ...thread], so a first comment that replies to an agent-written description (the PR #79 case) is detected asfollows-agent.agent-artifact: if no hard rule matched and the agent wrote the opening post, the comment still triggers. The seed then adds a line telling the agent to decide from context and to end the turn without posting if the comment isn't for it. Edits never use the new rules.detect()buildsopeningfrompayload.issue.job.threadstill holds only the real comments.I skipped the optional
issueBodyhelper in the dispatcher tests, because none of the new tests use it.Checks:
bun test src/forgejo src/bridgepassed (717 tests) andbun run typecheckpassed, both run inapps/server.Closes: #82