Integrations · GitHub
A labelled issue starts a change. A ready pull request starts a review.
The branch, the pull request and one check run land back under the App’s own identity — never a person’s token.
What starts work
Four events, in the API’s own spelling.
A label added to an issue starts a change — one per issue, linked once. A pull request marked ready starts a review run, narrowed by base branch where you want one. An @devbyte mention opens a review thread on the plan and resumes the build stage.
- 01
github.issue.labeleda label is added to a GitHub issue
scoped by label - 02
github.pull_request.readya GitHub pull request is marked ready for review
scoped by base_branch - 03
github.pull_request.commentsomeone mentions @devbyte on a GitHub pull request
- 04
github.check_run.faileda GitHub check run fails on a Factory pull request
What lands back
It lands back as a branch and a pull request under a per-run App token scoped to one repository, with one check run mirroring the quality checks, a tiered review anchored to file and line, and the audit trail linked from the body. Over budget, it arrives as several pull requests along the plan’s steps.
What you grant and why
A GitHub App, not a person and not a personal access token.
Subscribed to issues, issue comments, pull requests, review comments, check runs and installation events. The App’s private key never reaches an agent session, and an issue body, a diff or a comment arrives as data inside an untrusted-content fence, never as instruction.
- Contents · read and write
- To read the repository an agent session works in and your REVIEW.md, and to create the branches an over-budget diff is split into.
- Pull requests · read and write
- To open the change’s pull request, attach the audit trail to its body, and post the review.
- Issues · read and write
- To receive issues.labeled and write the status comment back onto the issue that started the change.
- Checks · read and write
- To create and update the one check run that mirrors the quality-check results.
- Metadata · read
- To list the installation’s repositories, so an automation can be scoped to one.
It never merges its own pull request.Nothing starts on a GitHub assignment — use a label — and only a person resolves a review thread. A replayed delivery returns 200 and does nothing.
Label an issue this week.
Install the App on one repository, scope an automation to it, and label the next ticket. The pull request arrives with its audit trail.