GitHub

Pie connects to GitHub in two ways, depending on what you want to automate. Pie Bot tests your pull requests and opens fixes for what it finds, and the Pie GitHub Action uploads new builds for testing. Most teams start with Pie Bot.

Pie Bot: Automated PR Testing

Pie Bot is the GitHub App (pie-pr-bot) that powers Pie Loop. Once it’s installed on a repository, it runs on every pull request with no setup per PR:

1. Reads the diff. Pie analyzes what changed and identifies which flows in your app are affected.
2. Tests like a user. AI agents navigate those flows, clicking and filling forms the way real users do.
3. Validates every finding against your source code, so no false positives reach you.
4. Reports back on the PR. Pie posts test results and status checks on the pull request, and opens a PR fix for any confirmed regression.
5. Updates Coverage Stories. Each run folds into your weekly Coverage Story: what shipped, what Pie tested, and what it found.

You don’t trigger any of this. Opening a pull request is enough.

What Pie Bot Can Access

When you install Pie Bot, GitHub asks you to grant:

Pie Bot does not store your source code, and it does not use your codebase to train any model. Access is scoped strictly to what’s needed to test PR diffs.

To get started, follow the Connect Pie Bot guide. Once it’s active, results appear in Coverage Stories.

Pie GitHub Action: Automated Build Uploads

If you test mobile builds, the Pie Build Uploader GitHub Action uploads a new .app or .apk to Pie whenever you publish a release, merge a pull request, or on a schedule, so your latest build is always tested.

See Automating Build Uploads (CI/CD) for the full setup.

Which One Do I Need?

Need Help?

• Support: support@pie.inc