What stays synchronized?

New commits, branches, tags, pull requests, issues, comments, reviews, reviewer requests, labels, and supported state changes synchronize after GitHub Sync is enabled.

Does setup merge existing issues and pull requests?

No. Existing unmatched issues and pull requests remain on their original platform. Matching numbers are not assumed to represent the same work. This avoids combining unrelated history without your approval.

Can I limit which branches sync back to GitHub?

Yes. Choose all branches and tags or configure a branch filter in repository settings. You can update the filter later.

What happens when GitHub is temporarily unavailable?

Trylle surfaces the failed connection and keeps supported outbound collaboration updates queued for retry. Restore GitHub access, then use Reconcile from repository settings.

Keep GitHub. Work in Trylle.

Connect a repository and both remotes stay writable. Your team reviews, runs CI, and ships here while everyone else keeps pushing to GitHub.

Get started Explore agents

GitHub sync

Keep commits, pull requests, issues, comments, reviews, and labels synchronized with GitHub.

Status

Trylle

acme/checkout

GitHub

acme/checkout

Sync behavior

Branch filtermain,release/*

Two-way sync is active

Syncing main,release/* on each commit.

Adopt it without moving off GitHub

Two-way sync keeps branches, tags, and history identical on both remotes. Teammates who never create an account keep pushing to GitHub, and their commits show up in your review here.

Sync runs both directions

Push to either remote. Both stay current, so nobody is cut off mid-sprint.

Import, don't re-create

Public or private repositories come across with their full history intact.

Discover why our GitHub Sync is awesome

What crosses, in both directions

GitHub's changes arrive by webhook; yours leave through a push mirror on every commit. Neither side becomes the read-only copy.

Every ref, or only the ones you name

Branches, tags, and commits move on each commit. Name a branch filter when you only want some of them leaving, and conflicting refs surface instead of overwriting either side.

Branches
Tags
Commits

Not just the code

The conversation travels with the code. Pull requests, issues, comments, reviews, requested reviewers, and labels stay connected after setup, including edits and state changes.

Pull requests
Issues
Comments
Reviews
Labels
Requested reviewers

Ship AI work your team can actually trust

Agent execution, review, permissions, and CI in one system. No credit card and no trial time. Just free.

Get started free — no card Explore repos