ci: add reusable Pi assignment-trigger workflow #10
No reviewers
Labels
No labels
dependencies
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
alex/.profile!10
Loading…
Reference in a new issue
No description provided.
Delete branch "pi/issue9-1783858666991"
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?
Summary
Adds a new reusable workflow (
.forgejo/workflows/pi-assign.yml) that reproduces the "Assignment Triggers" pattern from the pi-coding-agent-action README, adapted for Forgejo.How it works
issues: [assigned]andpull_request: [assigned]— fires when an issue or PR is assigned to someone.if: forgejo.event.assignee.login == 'pi'— only runs when the assignment target is thepibot user, ignoring all other assignments.workflow_callso every other repo on the forge can consume it the same way as the existingpi.yml:promptinput to instruct the agent to analyze the issue/PR, read the full discussion thread, and take appropriate action.Design choices
pi.ymlrather than merged — assignment triggers have different event types, conditions, and use apromptinstead of comment extraction, so keeping them separate is cleaner and avoids complicating the existing comment-based flow.@develop), secrets (PI_TOKEN,LLM_API_KEY), vars (PROVIDER,MODEL,THINKING_LEVEL,MY_FORGEJO_PUBLIC_URL), and extensions as the existingpi.ymlfor consistency.Fixes #9