Replies: 1 comment
|
Hi @kayahk , Thank you for the suggestion! We are actually planning to improve the GitHub plugin by leveraging the GitHub App Manifest Flow in an upcoming plugin update. Your feedback helps us confirm how important this feature is, so we’ll make sure to prioritize it in our next development cycle! |
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.
Context
We use Paca with several AI agents in one project: a developer agent that writes code and opens PRs, a reviewer agent, and a housekeeping agent. Paca's task flow, automations and agent triggers are a good fit for running a PR lifecycle that is almost fully autonomous: implement → open PR → independent review → handle feedback → merge. The GitHub integration is what holds us back.
Current state (as far as we can tell from the plugin tools)
github_set_token).COMMENT.github_set_token, or machine-user accounts that each cost a paid seat) are fragile or expensive.Proposal
1. Native GitHub App authentication
2. GitHub identity per agent (or per project member)
dev-agent → app-dev,reviewer-agent → app-reviewer,housekeeping-agent → app-janitor.3. Tools for the full PR lifecycle
expected_head_sha, so the merge fails if the PR changed after review4. GitHub events as automation triggers
pull_request(opened, ready_for_review, synchronize),pull_request_review,pull_request_review_comment,issue_commentandcheck_suite/check_runcompleted, plus conditions on the PR or checks. Then "new commits → re-review" and "new review comment → developer agent triages it" work without polling.Why this matters
These four pieces together make a governed autonomous workflow possible: the developer agent opens a PR, the reviewer agent formally approves or requests changes against the current head SHA, the developer agent handles the feedback, and a bot identity merges low-risk changes within branch protection. Every step is attributed to the right bot. Humans stay in the loop through branch protection rules rather than shared credentials.
Questions for maintainers
We're happy to test early builds and give feedback, or to help with parts of the implementation.
All reactions