Repository navigation
Replies: 1 comment
|
Pi Web does not appear to have a built-in Forgejo event listener or a comment-to-session resume workflow. It is a browser front end for local Pi sessions, and its contribution guide puts long-running background agents out of scope while pointing extension-sized features toward Pi extensions. One approach would be a separate Forgejo webhook receiver that validates each delivery, maps the repository and issue or PR to the right Pi session, then forwards the comment through a supported Pi interface. Restrict which Forgejo users can trigger it and ignore duplicate deliveries. I would keep the receiver separate from Pi Web’s local endpoint, since sessions can run tools with the host user’s privileges. Pi Web scope |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi I am using Pi Web and have my code in Forgejo (git). The agents are happy to raise PRs and issues, and even add new comments, but I was wondering if anyone knows how to make it so that a comment (from me) on the issue or PR will go into the conversation/session and resume working?
Is this possible?
All reactions