@junior: run on issue #24

2026-07-03T22:26:09+02:00

gitea-actions bot commented

2026-07-03 22:26:09 +02:00

Summary

Fix issue #23: newly created issues in ffaerber/agents now automatically trigger @pm, matching the behavior already working in ffaerber/homelab.

Changes

.gitea/workflows/ai-agent.yml: added issues: types: [opened] trigger alongside the existing issue_comment trigger so the shared agent.yml workflow is invoked on new issues and can route them to @pm.

Resolves #23 · 🤖 @junior

## Summary Fix issue #23: newly created issues in `ffaerber/agents` now automatically trigger `@pm`, matching the behavior already working in `ffaerber/homelab`. ## Changes - `.gitea/workflows/ai-agent.yml`: added `issues: types: [opened]` trigger alongside the existing `issue_comment` trigger so the shared `agent.yml` workflow is invoked on new issues and can route them to `@pm`. --- Resolves #23 · 🤖 @junior

gitea-actions bot added 1 commit 2026-07-03 22:26:09 +02:00

@junior: issue #23 — trigger @pm on new issues in this repo 3ad5c28243

gitea-actions bot commented

2026-07-03 22:26:10 +02:00

🤖 @junior — ✅ PR ready for review — @ffaerber please review & merge:

ffaerber/agents#24

🤖 **@junior** — ✅ PR ready for review — @ffaerber please review & merge: - https://git.ffaerber.duckdns.org/ffaerber/agents/pulls/24

gitea-actions bot commented

2026-07-03 22:26:10 +02:00

🤖 @junior — activity log (19 entries):

tool calls & reasoning

🔧 bash: git status && git branch --show-current
🔧 glob: 🔧 **glob**:
🔧 glob: ``
🔧 bash: ls -la
🔧 bash: find "/workspace/ffaerber/agents/.gitea" -type f
🔧 read: .gitea/workflows/ai-agent.yml
🔧 read: .gitea/workflows/agent.yml
🔧 edit: .gitea/workflows/ai-agent.yml
🔧 bash: git diff && git add .gitea/workflows/ai-agent.yml && git commit -m "@junior: issue #23 — trigger @pm on new issues in this repo" && git push
💬 Done. The caller workflow in ffaerber/agents was only listening to issue_comment, so new issues never reached the shared agent workflow. I added the issues: opened trigger to .gitea/workflows/ai-agent.yml; the shared agent.yml already has routing that defaults new issues to @pm and the ffaerber-author gate, so it will behave like ffaerber/homelab.

BEGIN_PR_DESCRIPTION

Summary

Fix issue #23: newly created issues in ffaerber/agents now automatically trigger @pm, matching the behavior already working in ffaerber/homelab.

Changes

.gitea/workflows/ai-agent.yml: added issues: types: [opened] trigger alongside the existing issue_comment trigger so the shared agent.yml workflow is invoked on new issues and can route them to @pm.
END_PR_DESCRIPTION

🤖 **@junior** — activity log (19 entries): <details> <summary>tool calls & reasoning</summary> 🔧 **bash**: `git status && git branch --show-current` 🔧 **glob**: `` 🔧 **glob**: `` 🔧 **glob**: `` 🔧 **bash**: `ls -la` 🔧 **bash**: `find "/workspace/ffaerber/agents/.gitea" -type f` 🔧 **read**: `.gitea/workflows/ai-agent.yml` 🔧 **read**: `.gitea/workflows/agent.yml` 🔧 **edit**: `.gitea/workflows/ai-agent.yml` 🔧 **bash**: `git diff && git add .gitea/workflows/ai-agent.yml && git commit -m "@junior: issue #23 — trigger @pm on new issues in this repo" && git push` 💬 Done. The caller workflow in `ffaerber/agents` was only listening to `issue_comment`, so new issues never reached the shared agent workflow. I added the `issues: opened` trigger to `.gitea/workflows/ai-agent.yml`; the shared `agent.yml` already has routing that defaults new issues to `@pm` and the `ffaerber`-author gate, so it will behave like `ffaerber/homelab`. BEGIN_PR_DESCRIPTION ## Summary Fix issue #23: newly created issues in `ffaerber/agents` now automatically trigger `@pm`, matching the behavior already working in `ffaerber/homelab`. ## Changes - `.gitea/workflows/ai-agent.yml`: added `issues: types: [opened]` trigger alongside the existing `issue_comment` trigger so the shared `agent.yml` workflow is invoked on new issues and can route them to `@pm`. END_PR_DESCRIPTION </details>

ffaerber merged commit 9760d3b652 into main

2026-07-03 22:28:17 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: gitea/agents#24