Unsupported Features: GitHub

Here's a breakdown of what Unito's GitHub integration can't do yet and a few other considerations.

In this article:

Need something this integration doesn't support yet? We can help you work around many of these limitations. Meet with us to find out how.

Subtasks: Since GitHub only supports parent tasks, Unito can't sync subtasks or checklists from other tools to GitHub.

GitHub labels with some fields: Because GitHub's label field is a multi-value dropdown, it can only be mapped to other multi-value dropdown fields, like other label fields.
Comments and descriptions can't sync to text-based fields in tools such as Google Sheets or Microsoft Excel. You can only sync comments with other tools that have comment functionality.
Mapping pull requests to subtasks: This mapping is unavailable.
Edited comments: When you edit comments in GitHub, these edits won't be synced over to other repositories or other tools. That's because Unito only syncs new comments, not any edits to existing comments.

GitHub projects: Unito doesn't support GitHub projects. Issues connected to both a repo and a project will continue to sync, but you can't select a GitHub project as a block of work.
Permissions: Unito needs certain read & write permissions in order to work. You can get a full breakdown of these permissions here.
On-premise: In order for on-premise GitHub accounts to connect to Unito, it needs to be accessible via the internet. If that isn't the case, please read our guide to set this up, or contact us if you’re not sure how to proceed!
Making changes in GitHub under your own name: Unito integrations take actions in your GitHub projects using an account called sync-by-unito. Unfortunately, due to a limitation in GitHub's API, you can't change this name to something else.