gitea/agents
8
0
Fork 0
Code Issues 2 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

run on issue #23

New Issue
Closed
opened 2026-07-03 22:24:30 +02:00 by ffaerber · 6 comments
ffaerber commented 2026-07-03 22:24:30 +02:00
Owner
Copy Link
Copy Source

if i add a new issue pm should start
this is also working in ffaerber/homelab
but its not working in ffaerber/agents

if i add a new issue pm should start this is also working in ffaerber/homelab but its not working in ffaerber/agents
ffaerber commented 2026-07-03 22:24:34 +02:00
Author
Owner
Copy Link
Copy Source

@pm here

@pm here
🚀 1
gitea-actions bot commented 2026-07-03 22:24:51 +02:00
Copy Link
Copy Source

🤖 @pm

The issue reports that the automation to trigger @pm when a new issue is created is not working in the ffaerber/agents repository, although it works in ffaerber/homelab.

Since this repository contains the shared AI-agent workflow (.gitea.workflows/agent.yml) used by other repos, a failure here likely indicates a problem with the trigger configuration or the workflow definition itself.

Plan:

  1. Research: Investigate .gitea/workflows/agent.yml to identify the trigger for new issues and compare it with the expected behavior.
  2. Fix: Correct the workflow trigger to ensure @pm is automatically invoked on new issues.
  3. Verification: Since this is a workflow trigger, verification will require creating a test issue or simulating the event.

I propose that @junior handles this, as it is likely a small change to a YAML configuration file.

@ffaerber ready to start building? reply yes to proceed.

🤖 **@pm** The issue reports that the automation to trigger `@pm` when a new issue is created is not working in the `ffaerber/agents` repository, although it works in `ffaerber/homelab`. Since this repository contains the shared AI-agent workflow (`.gitea.workflows/agent.yml`) used by other repos, a failure here likely indicates a problem with the trigger configuration or the workflow definition itself. **Plan:** 1. **Research:** Investigate `.gitea/workflows/agent.yml` to identify the trigger for new issues and compare it with the expected behavior. 2. **Fix:** Correct the workflow trigger to ensure `@pm` is automatically invoked on new issues. 3. **Verification:** Since this is a workflow trigger, verification will require creating a test issue or simulating the event. I propose that **@junior** handles this, as it is likely a small change to a YAML configuration file. @ffaerber ready to start building? reply yes to proceed.
ffaerber commented 2026-07-03 22:25:15 +02:00
Author
Owner
Copy Link
Copy Source

@pm yes

@pm yes
🚀 1
gitea-actions bot commented 2026-07-03 22:25:31 +02:00
Copy Link
Copy Source

🤖 @pm

Handing off to @junior.

🤖 **@pm** Handing off to @junior.
ffaerber commented 2026-07-03 22:25:31 +02:00
Author
Owner
Copy Link
Copy Source

@junior please proceed with issue #23 per the plan above (delegated by pm).

@junior please proceed with issue #23 per the plan above (delegated by pm).
🚀 1
gitea-actions bot commented 2026-07-03 22:25:38 +02:00
Copy Link
Copy Source

🔨 @junior is on it — building on branch ai/issue-23. I'll open a PR when it's ready.

🔨 **@junior** is on it — building on branch [`ai/issue-23`](https://git.ffaerber.duckdns.org/ffaerber/agents/src/branch/ai/issue-23). I'll open a PR when it's ready.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
autopilot
run agents without asking
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
ffaerber hermes intern junior lead ops (Ops Agent) pm qa (QA Agent) senior
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gitea/agents#23