Add pi assign workflow #3
Labels
No labels
dependencies
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
alex/base-template#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
See https://forge.l3x.in/alex/.profile/src/branch/master/.forgejo/workflows/pi-assign.yml
/pi new pr
I'll start by understanding the current repository structure and the reference workflow file.Now I understand the pattern. The existing
pi.ymlwraps the reusable workflow fromalex/.profile. I need to create an analogouspi-assign.ymlwrapper that calls thepi-assign.ymlreusable workflow on assignment events.PR #4 created: #4Added
.forgejo/workflows/pi-assign.ymlas a thin wrapper around the reusable workflow atalex/.profile/.forgejo/workflows/pi-assign.yml@master. It triggers onissues: [assigned]andpull_request: [assigned]events, mirroring the same structure as the existingpi.ymlwrapper (which wrapspi.ymlfor 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)