GitHub
Connect
Connect GitHub from the terminal. Pass --help for the flags GitHub accepts.
polylane integration connect --type githubInstall the Polylane GitHub App on your organization.
Install the Polylane GitHub App to give agents your code, an impact assessment on each pull request, and fixes as pull requests. You choose which repositories Polylane can read, and there are no tokens to manage.
- Click Connect GitHub. GitHub opens the install page of the Polylane GitHub App.
- Choose the organization or account to install it on.
- Give access to all repositories or select specific ones. You can change this selection in GitHub later.
- Approve the installation. GitHub sends you back to Polylane, and Polylane starts to sync your repositories.
If the app is already installed on the account, Polylane links that installation and keeps the repositories that you selected on GitHub. To add repositories later, open Settings > Repositories and choose Add repository. This opens the app settings on GitHub.
How it works
Repositories and code
Polylane syncs each repository that the app can read and links it on the topology to the resources that it deploys. A push to the default branch syncs that repository again. A daily sweep reads the repository selection of the installation. A repository that you remove from the app becomes unavailable, and its history stays.
Agents clone a repository into a sandbox to search and run its code. They read files, commits, pull requests and CI runs through GitHub.
Impact assessments
Each pull request against the default branch gets an impact assessment when it opens, gets new commits, or leaves draft. An agent checks the change against live metrics, logs and open issues for the resources that the repository deploys. Polylane writes one comment with a pass or fail verdict and updates it after each push. It also posts the Polylane production impact check, which fails on a fail verdict. Require that check in branch protection to block a merge.
While security reviews are on, the same run reviews the code that the pull request adds for security flaws. It posts the Polylane security review check, which fails on a confirmed critical or high finding. Turn security reviews off in Settings > Impact assessments.
Mention @polylane in a comment to ask a question, get a new assessment, or ask for a fix. A pull request from another bot gets an Assess with Polylane button instead of an automatic assessment. After 10 automatic assessments on one pull request, Polylane stops automatic assessments for it.
Fix pull requests
When a fix run confirms a cause in a connected repository, Polylane opens a pull request from a branch that starts with polylane/. It asks the reviewers set on the repository, then the owners of the affected resource or repository, then at most two reviewers that GitHub suggests. A comment on the pull request starts a follow-up change. When a check fails, Polylane reads the failure and pushes a fix, up to three times.
After a week with no activity, Polylane sends one reminder. After one more quiet week, it closes the pull request and keeps the branch.
On connect, Polylane opens one Set up Polylane pull request in your most active repository. It adds a Polylane section to the agent instruction file, such as AGENTS.md.
CI failures
When a GitHub Actions workflow or the check suite of another app fails on the default branch, Polylane receives an alert, and the alert becomes an issue. The next success on that branch recovers it.
Settings
| Setting | Where | What it controls |
|---|---|---|
| Assess pull requests for production impact | Repository settings | Impact assessments for one repository. Settings > Impact assessments turns them off for the workspace. |
| Block merging on production concerns | Repository settings | The Polylane production impact check. On by default. |
| Impact assessment instructions | Repository settings | Guidance that the agent reads for each assessment, such as deploy-critical paths. |
| Open autofix pull requests | Repository settings and the Autofix card of the workspace settings | Fix pull requests. Pull requests that are open stay open. |
| Reviewers | Repository settings | The people and teams that Polylane asks first on a fix pull request. |
Disconnecting
Uninstall the Polylane GitHub App under Settings → GitHub Apps in your GitHub organization. Polylane then removes the repositories of that installation and marks its open fix pull requests as unreachable. Disconnecting in Polylane removes the repositories from this workspace only. The app stays installed on GitHub, because other workspaces can use the same installation.
These items stay in GitHub after you disconnect: the polylane/onboarding/* branch and the Set up Polylane pull request, the branches and pull requests of fixes, and the check runs on past commits.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Polylane held. Polylane removes what GitHub's API lets it remove. The following stays until you remove it yourself:
- polylane/onboarding/* branch and Set up Polylane PR
- autofix branches and PRs
- check runs on past commits
GitHub is connected through an app installation, so disconnecting happens on GitHub's side: uninstall the Polylane app from your installed GitHub Apps. Polylane is notified and removes the integration.
Tools
9Operations agents can perform in threads.