What this article covers:

  • What is synced between GitHub projects

  • What isn't synced

  • GitHub-GitHub sync customization options

This article is out of date. You can find the updated version of this article here.

Collaboration between two private or public repos has never been easier! Now, with Single App Sync, you can work with another repos without having to request access to their entire GitHub organization. Check out the guide below for what we sync, and how we sync it.

What is synced?

See a field you would like to sync that is not listed? Contact us - we may already support it through a manual configuration.

What is not synced?

Do you have a feature you would really like? Contact us! we prioritize based on user requests.

Customization options

Here are all the available options for GitHub:

Filter by label

Unito will sync all tasks and issues by default but you can customize your workflow by syncing just some of them (complete guide).

Filter by issue type

You can filter which type of issues you want to be synced between projects (Issue, Pull-Request, or both) (complete guide).

One-way sync

You can choose to sync only from one GitHub project to another. Here is how it works.

Map your GitHub users

Here is a complete article on how to sync teammates.

Sync tasks/issues already closed

Unito will automatically sync opened tasks or issues automatically. But here is how to also sync closed tasks and issues prior to the sync creation.

Add GitHub issue number to task title

Unito doesn't sync the issue number to the opposite Github project by default but you can enable that in your sync settings under the relevant GitHub tab. Here is how to do it.

Did this answer your question?