Add assign Pi auto trigger workflow #9

New issue

Closed

opened 2026-07-12 12:15:05 +00:00 by alex · 2 comments

alex commented

2026-07-12 12:15:05 +00:00

Owner

Read forgejo action specs, reproduce the "Assignment Triggers" flow from https://github.com/shaftoe/pi-coding-agent-action readme adding a new shareble workflow in this repo.

Notice that this has to apply only when the assigned user is 'pi'

Read forgejo action specs, reproduce the "Assignment Triggers" flow from https://github.com/shaftoe/pi-coding-agent-action readme adding a new shareble workflow in this repo. Notice that this has to apply only when the assigned user is 'pi'

alex commented

2026-07-12 12:15:51 +00:00

Author

Owner

/pi new PR

pi referenced this issue from a pull request that will close it,

2026-07-12 12:17:48 +00:00

ci: add reusable Pi assignment-trigger workflow #10

pi commented

2026-07-12 12:17:54 +00:00

Contributor

Now let me fetch the README from the pi-coding-agent-action repository to understand the "Assignment Triggers" flow.Now I have a clear picture. The existing pi.yml handles comment-based interactive triggers. I need to create a new reusable workflow that reproduces the "Assignment Triggers" pattern, firing when an issue/PR is assigned to pi. Let me check the Forgejo event payload specs for assignment events to make sure I use the right context path.I have everything I need. Now let me create the new reusable workflow file:Now let me create the PR:PR #10 created: #10

The new workflow (.forgejo/workflows/pi-assign.yml) reproduces the "Assignment Triggers" pattern from the pi-coding-agent-action README:

Triggers on issues: [assigned] and pull_request: [assigned] events
Only fires when the assignee is pi (if: forgejo.event.assignee.login == 'pi')
Reusable via workflow_call so other repos can call it with uses: alex/.profile/.forgejo/workflows/pi-assign.yml@master
Uses a prompt (instead of comment extraction) since assignment events have no comment body
PR-aware checkout — checks out the PR head branch for PR assignments, default ref for issues
Mirrors the existing pi.yml configuration (same secrets, vars, extensions, action version)

Now let me fetch the README from the pi-coding-agent-action repository to understand the "Assignment Triggers" flow.Now I have a clear picture. The existing `pi.yml` handles comment-based interactive triggers. I need to create a new reusable workflow that reproduces the "Assignment Triggers" pattern, firing when an issue/PR is assigned to `pi`. Let me check the Forgejo event payload specs for assignment events to make sure I use the right context path.I have everything I need. Now let me create the new reusable workflow file:Now let me create the PR:PR #10 created: https://forge.l3x.in/alex/.profile/pulls/10 The new workflow (`.forgejo/workflows/pi-assign.yml`) reproduces the "Assignment Triggers" pattern from the pi-coding-agent-action README: - **Triggers** on `issues: [assigned]` and `pull_request: [assigned]` events - **Only fires** when the assignee is `pi` (`if: forgejo.event.assignee.login == 'pi'`) - **Reusable** via `workflow_call` so other repos can call it with `uses: alex/.profile/.forgejo/workflows/pi-assign.yml@master` - Uses a **prompt** (instead of comment extraction) since assignment events have no comment body - **PR-aware checkout** — checks out the PR head branch for PR assignments, default ref for issues - Mirrors the existing `pi.yml` configuration (same secrets, vars, extensions, action version) --- [View action run](https://forge.l3x.in/alex/.profile/actions/runs/10) | Model: zai/glm-5.2 (thinking: xhigh) | Time: 2m 4s | Tokens: 152.8K | Pi SDK v0.80.3 | Action v2.25.1-develop (develop @ 1027378)

alex closed this issue

2026-07-12 12:27:09 +00:00

No labels

dependencies

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

alex/.profile#9

No description provided.

Rows
Columns