Add pi assign workflow #3

Closed
opened 2026-07-12 12:29:29 +00:00 by alex · 2 comments
Owner
See https://forge.l3x.in/alex/.profile/src/branch/master/.forgejo/workflows/pi-assign.yml
Author
Owner

/pi new pr

/pi new pr
Contributor

I'll start by understanding the current repository structure and the reference workflow file.Now I understand the pattern. The existing pi.yml wraps the reusable workflow from alex/.profile. I need to create an analogous pi-assign.yml wrapper that calls the pi-assign.yml reusable workflow on assignment events.PR #4 created: #4

Added .forgejo/workflows/pi-assign.yml as a thin wrapper around the reusable workflow at alex/.profile/.forgejo/workflows/pi-assign.yml@master. It triggers on issues: [assigned] and pull_request: [assigned] events, mirroring the same structure as the existing pi.yml wrapper (which wraps pi.yml for comment-triggered invocations).


View action run | Model: zai/glm-5.2 (thinking: xhigh) | Time: 36s | Tokens: 27.2K | Pi SDK v0.80.3 | Action v2.25.1-develop (develop @ 1027378)

I'll start by understanding the current repository structure and the reference workflow file.Now I understand the pattern. The existing `pi.yml` wraps the reusable workflow from `alex/.profile`. I need to create an analogous `pi-assign.yml` wrapper that calls the `pi-assign.yml` reusable workflow on assignment events.PR #4 created: https://forge.l3x.in/alex/base-template/pulls/4 Added `.forgejo/workflows/pi-assign.yml` as a thin wrapper around the reusable workflow at `alex/.profile/.forgejo/workflows/pi-assign.yml@master`. It triggers on `issues: [assigned]` and `pull_request: [assigned]` events, mirroring the same structure as the existing `pi.yml` wrapper (which wraps `pi.yml` for comment-triggered invocations). --- [View action run](https://forge.l3x.in/alex/base-template/actions/runs/1) | Model: zai/glm-5.2 (thinking: xhigh) | Time: 36s | Tokens: 27.2K | Pi SDK v0.80.3 | Action v2.25.1-develop (develop @ 1027378)
alex closed this issue 2026-07-12 12:38:22 +00:00
Sign in to join this conversation.
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/base-template#3
No description provided.